Free openxava eclipse plugins software for linux

CodeSugar Eclipse Plugin is an Eclipse plugin that can generate methods such as equals(), clone(), toString(), and hashCode() for Java classes.
Enhancements:
- This release includes many feature enhancements in generated code, as well as UI refinements like enabling actions in the menu only when a type of .java file is selected.

Lint4j is a static Java source code analyzer that detects locking and threading issues, performance and scalability problems, and checks complex contracts such as Java serialization by performing type, data flow, and lock graph analysis.

Lint4j features command line, Ant, Maven, Eclipse, and Emacs integration.

Eclipse plugin for Qt manages the generation of Makefiles from .pro files and compilation with make.
Eclipse plugin for Qt is experimental, which means there is currently a limited number of features. Yet, it should provide you with the basis for compiling a Qt project. It is based on CDT for the C++ part.
Unfortunately, CDT has not yet reached the level of usability of Eclipse for Java. This becomes particularly noticeable with Qt, in particular regarging code completion, which I had to disable (see Known bugs and limitations). Fortunately, the soon-to-be released Callisto project should make a big step in the good direction.
This plugin has been tested with Eclipse 3.1.2 and CDT 3.0.2. Testing with Callisto will be done after release candidates.
Main features:
- Project type for Qt
- Builder for managing qmake
- Dedicated console
- Problems reporting
- Editor for .pro files
- Configurable syntax highlighting
- Content assist for variables
- Problems reporting

Tiny Eclipse project was created to provide small and easy to install distributions of Eclipse.
Main features:
- Small download size
- Cross-platform GUI installer(current only for win32 & linux-gtk)
- You can choose the features you want to install.
Enhancements:
- This is based on the Eclipse 3.3 code base.

Custom Eclipse Builder is a lightweight Ant-based project to build a company and personal customized Eclipse distribution including company and personal relevant plugins, preferences and settings.
The modern software development process becomes more and more distributed characted. Now, a usual project is not a one-men work more, but a collective work of bunch of people communicating through network. Therefore, its very important that each involved developer stands to the rules and guidelines applied for the project.
There are many tools that makes the development process easy. One of these tools that increases in popularity more and more is Eclipse. The number of companies, organizations or project teams using Eclipse grows permanently. Typically, in such a company a developer takes itself care of downloading and configuring Eclipse and all kinds of Plugins.
Therefore, the more developers using Eclipse within of organization the more different versions, configurations and settings do exist. When a group of developers is working for a project and sharing the projects resources (and this is the typical case) using of different tools and versions may lead to any kinds of conflicts (unfortunately this is the typical case too).
The Custom Eclipse Builder is a very easy way to solve all these problems. After you have installed and configured Builder you can build your own Eclipse distribution each time you wish (e.g. by scheduling a cron job) in just a few minutes. The Builder will download all desired Eclipse- and plugins distributions full automatically.
There is no need to check a new plugins version you wish to include in the distribution is realised. The Custom Eclipse Builder takes care of plugins version management. Once installed and configured you can use Builder over a couple of months without any modifications.
Enhancements:
- This release fixes some minor bugs and supports building distributions based on Eclipse 3.2M1, 3.2M2, and 3.2M3.

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.