Free ides software for linux

Jikes RVM is a compiler that translates JavaTM source files as defined in The Java Language Specification into the bytecoded instruction set and binary format defined in The Java Virtual Machine Specification.

You may wonder why the world needs another Java compiler, considering that Sun provides javac free with its SDK. Jikes has five advantages that make it a valuable contribution to the Java community: [OSI Certified Logo]

* Open source. Jikes is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative.
* Strictly Java compatible. Jikes strives to adhere to both The Java Language Specification and The Java Virtual Machine Specification as tightly as possible, and does not support subsets, supersets, or other variations of the language. The FAQ describes some of the side effects of this strict language conformance.
* High performance. Jikes is a high performance compiler, making it ideal for use with larger projects.
* Dependency analysis. Jikes performs a dependency analysis on your code that provides two very useful features: Incremental builds and makefile generation.
* Constructive Assistance. Jikes strives to help the programmer write better code in two key ways. Jikes has always strived to provide clear error and warning text to assist the programmer in understanding problems, and now with release 1.19 Jikes helps point out common programming mistakes as documented in Effective Java.

Abridged from a FAQ entry which was adapted from some material by Lou Grinzo for an article he wrote.

The fact that Jikes is a high-performance, highly compatible Java compiler that can be used on almost any computing platform makes it an interesting program and worth investigating for almost any Java programmer. But Jikes is also notable because it lies at the center of two events: the adoption of open source philosophy and practice by large corporations, and the continued growth of Java for Linux.

Its worth pointing out that Jikes is not, and is not intended to be, a complete development environment -- it is simply a command line compiler. It should not be considered a replacement for more complete tools, such as Source Navigator or IBMs VisualAge for Java which provide sophisticated graphical IDEs (Integrated Development Environments).

The Jikes compiler was released in binary form in April 1997 on the IBM alphaWorks site. Jikes for Linux was released on 15 July 1998. The response was overwhelming -- Jikes had more downloads in the three months after the announcement than in the fifteen months before the announcement.

Around the end of March 2002, IBM opened a fledgling community hosting location attached to their developerWorks site with Jikes as a founding member. Approximately 3 years later this server was decommissioned and the most active projects migrated into SourceForge.net hosting options. During those three years Jikes was the #1 most popular project every month, often by a large margin. We approached nearly 250,000 downloads while residing at dw/oss, and had been consistently tallying triple digit daily downloads.

Release of Jikes for Linux was soon followed by requests to open up the source. Many notes and comments from users suggested this would be a good idea. The source was released under a liberal license in December 1998 to make a very visible demonstration of IBMs commitment to open standards and to Java Technology, to make Jikes more reliable and accessible, to encourage more widespread use of Java Technology, to encourage standardization of Java Technology, and to gain some experience actually running an open source project. This marked the start of one of IBMs first efforts in the open source arena.

The original alphaWorks version of Jikes was written by Philippe Charles and Dave Shields of the IBM T. J. Watson Research Center. For awhile after the release of the source they continued to work on the compiler as contributors; however, shortly after the project migrated to developerWorks Open Source Server they were officially moved off onto other projects within IBM. Today there are no IBMers who work on Jikes as part of their job description. Jikes survives today soley based on the free time contributions of members of the open source community.

The source code is available under IBMs Public License, which has been approved by the OSI (Open Source Initiative) as a fully certified open source license. The project provides access to the complete CVS development tree, which includes not only Jikes, but also the source for the Jacks Test Suite and the Jikes Parser Generator used to build Jikes. Jikes is included in many Open Source Operating Systems. The Jacks Test Suite is a replacement for the Jikestst package.

Ant-Eclipse is a task for the Java build tool Ant generating Eclipse projects to be just imported and used easily. Ant build scripts are used as a central place for the configuration of sources and libraries which the generated projects are based on.
The most usual way to develop a software is to write, run and debug the source code in an IDE. However, as long as the first source files are compilable the software finds its way into a package and it must be possible to compile it, run it and test it in other environments where the IDE is not available. Build tools used for this job usually cannot read the project files where IDEs store information about packages and sometimes there are more IDEs used by developers. It seems obvious that the build tool needs its own description of the package.
Keeping the package configuration on two places is more error-prone and looking for errors caused by diffrerences in these configurations can cost much time when the error occur first during the run-time of an application.
It is allways the better to keep the configuration on a single place and not to maintain its copies on more places. If there are more tools used for the development one of them should be chosen as the owner and provider of the package configuration. The others have to base ther configuration on this central one either by using it directly or by refreshing their one if the central one changes.
Which tool is the best one for keeping the package configuration? It depends on the package and the development process. The most important tool is usually the one which automates compiling packaging and running tests because it produces the final package to be delivered to end-users. This automated production usually runs unattendedly reporting results from processing the current source code base. The configuration of this tool can be taken as the source for all the others.
Ant is the most favourite build tool for projects written in the Java language. Eclipse with JDT is a state-of-the-art IDE for Java developers. Unfortunately, Eclipse cannot use Ant build scripts to base configuration of its projects on them. Ant can be run from the Eclipse IDE but the configuration is kept separately.
Ant-Eclipse automates the task of creating an Eclipse project making the developer to write an automated build script as the first thing and to generate an Eclipse project from it whenever it changes. It keeps the Eclipse project always up-to-date with the last changes in the build script. This project refreshing is usually automated when more developers are working on a software project. They have to synchronize regularly their workspace with a central source code repository to integrate changes made by the others. This usually involves:
Synchronizing the source code with a central repository.
Updating the binary dependencies (libraries) from a central depot.
Generating resources (files) dependent on the environment (time and place where it runs) like build numbers, package manifests and so on.
The regeneration of Eclipse projects fits exactly to the last phase of such sychronizing process. This is the recommended usage of the Ant-Eclipse task.
A formerly existing Eclipse project will be overwritten if a new one is to be generated. Files for an Eclipse project are not generated if they exist and they are not older than the Ant build script (the Ant build script has not been changed). This update can be forced, however.
Enhancements:
- The tool has been used for over a year, and is considered a stable version.

iloog project is a Gentoo-based LiveCD produced by the Ioannina Linux User Group (I.L.U.G.), targeted mainly at students and scientists.
Our purpose is to create a multi-purpose tool that will suit the needs of our growing user-base through a continuous ad-hoc process that follows the "release early, release often" paradigm.
Main features:
- ISOLINUX boot loader for increased compatibility with older hardware
- UnionFS filesystem support that enables you to write everywhere on the LiveCD and install extra packages
- Graphical X environment through the Fluxbox window manager (see the screenshots)
- Many programming editors and IDEs, including: Vim, nano, Anjuta, Kdevelop
- A plethora of scientific applications, including: Octave, Namd, Tinker, Merlin
- Fits, conveniently, in a 700MB CD

DBG is a a full-featured php debugger, an interactive tool that helps you debugging php scripts.
It works on a production and/or development WEB server and allows you debug your scripts locally or remotely, from an IDE or console.
Main features:
- native debugger. Works transparently, neither script nor PHP engine modifications required.
- server part (dbg module) runs on all platforms where PHP itself runs.
- works transparently across the global network as well as locally.
- JIT. When enabled can start debugging Just In Time of error occurs.
- supports back-tracking, e.g. displays a list of all procedures with their local variables, the current execution position reached from. Also you can watch local variables or function parameters in all active and nested scopes.
- certainly, you can execute script in the debugger step by step (step-in, step-out, step-over...), evaluate any valid php expressions or complex variables, modify values of any variables on the fly and create any new ones. Breakpoints can be conditional, they also may skip entered number of hits.
- has embedded profiler, so now its easy to find out a bottleneck in the scripts.
- allows multiple debugger processes running simultaneously.
- compatible with php-4.0.6 and higher.
- has open COM interfaces for integration with win32-based 3rd party IDEs.
- Commercial version of DBG (2.16.x) is available with commercial version of PHPEd PHP IDE only, see review for details.
- Linux, BSD, SunOs, MacOs and Win32 platoforms are supported.
- Free version (2.11.x) is available on this site. It works with PHP Edit, PHP Coder and some other IDEs.
- Free dbg front-end (dbg-cli) for Linux/Unix can be used to debug scripts either directly or under DDD 3.3.9 (GNU debugger). Also see RedHat 7.3, YellowDog and Mandrake distributions at RPM Find site.
Enhancements:
- All php versions from 4.0.6 up to 4.3.10 and from 5.0.0 up to 5.0.3 are supported.
- Support for HARDENED php v0.2.6 added (4.3.9h, 4.3.10h and 5.0.3h).
- Command line interface (dbg-cli) improved.
- Tested with php 4.0.6, 4.1.0-4.1.2, 4.2.0-4.2.3, 4.3.0-4.3.10, 5.0.0-5.0.3.

Domino Javadoc Generator project aims to create a documentation to the Lotus Notes API for Java in a standard format common in the Java comunity and accepted by the most IDEs for Java.

The Lotus Notes API is delivered as a Java archive together with the original documentation in the native format of a Domino database with the IBM Domino Designer. The documentation can be read only in the Lotus Notes. Java-oriented tools cannot use it to display a description of a Java class, to browse classes and their methods or to offer an automatic code insertion based on a Java object and its class.

The goal is to create a Javadoc documentation together with a pseudo-source code of the Lotus Notes API. The documentation can be viewed, indexed and integrated to IDEs. The pseudo-source code can be integrated to IDEs to support object browsing and automatic source code insertion.

ScitePM is a lightweight, Gtk-based project manager for use with the SciTE editor. It allows the user to organize a set of files as a project, like most IDEs, and then open them within SciTE.
ScitePM uses the SciTE "Director" interface to communicate with SciTE. Note also that SciTE must be named "SciTE" or "scite" to allow ScitePM to correctly launch it. If this is not the case on your system, create a symlink something like this:
ln -s /usr/local/bin/scite_exec_blah_blah ~/bin/scite (Obviously that assumes that SciTE is /usr/local/bin/scite_exec_blah_blah on your system)
Usage:
ScitePM is very simple to use. Click the "Open Project," "Save Project," or "Add Files" buttons to do the obvious things. Right-click on the main pane of the app to add files or groups (i.e. folders). Drag and drop folders and files within the app to arrange to your satisfaction.
To open a file, double-click it or highlight it and press return/enter. Note that the SciTE executable must be named "SciTE" for ScitePM to launch it!
The command line syntax for scitepm is:
scitepm [-q|--quiet] [-v|--version] [-h|--help] [project-path]
-q | --quiet = do not show the "About" dialog at startup.
-v | --version = print the application version to stdout at startup
-h | --help = print the usage (what youre reading now) to stdout
[project-path] = the path to a ScitePM project file to load at startup
Enhancements:
- rrwood - 2006/05/27 - Activate SciTE via "_NET_ACTIVE_WINDOW" message to ewmh-compliant window manager