Free openxava eclipse plugin 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.

Docbkx Maven Plugin project provides a number of tools for supporting DocBook in a Maven environment. This may seem odd to you, since
1) Maven 2 is supposed to support DocBook natively, relying on Doxia, and
2) there is already another DocBook plugin at mojo.codehaus.org.
The thruth however is that DocBook support in Doxia is fairly limited, mainly because Doxia as a framework supports only a small fraction of the concepts found in DocBook. The subset of DocBook supported by Doxia is not even close to simplified DocBook.
The DocBook plugin at mojo.codehaus.org is supporting a wider range of DocBook markup, and is in fact more similar to the DocBook tools provided with this project. There are however some significant differences:
- The focus is on ease of use.
- You should not be required to install additional stuff to your hard disk in order to generate content from your DocBook sources. Simply adding a reference to the plugin in your POM should be sufficient.
- This project focuses on providing dedicated support for particular DocBook XSL stylesheet distributions. That means you can rely on the dedicated parameterization mechanism of Maven Plugins to pass in the XSLT parameters defined for a particular version and type of XSLT stylesheet.
- In the DocBook Plugin found at mojo.codehaus.org, you will be required to download a specific version of the DocBook XSL stylesheets manually. The plugins packaged contain the stylesheets as well. (In this project, a particular version of the stylesheets is closely tied to a particular version of the plugin. That you means you can always rely on the plugins documentation to know which parameters you could pass in.)
- The DocBook plugin found at mojo.codehaus.org requires you to have access to the Internet in order allow the plugin to resolve URIs. The plugins provided in this project act differently: if your DocBook sources are referening to a DTD, then you can simply add a dependency to a jar file containing the DTD and related entities, and the plugin will make sure that all references will be resolved correctly.
Enhancements:
- Support for Eclipse help files was added.

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.

WebScarab for Eclipse is an extensible framework for analyzing applications that communicate using the HTTP protocol.
It includes an HTTP monitor and an HTTP proxy for recording all messages between your machine and remote servers.
It is a port to Eclipse of the WebScarab application from OWASP.
It consists of the following components:
Proxy: HTTP proxy that monitors HTTP communication.
Triggers: Eclipse extensions and user scripts that are executed on specific message patterns.
HTTP Summary View: Eclipse view that shows all recorded messages with the ability to save and edit the message content.
Main features:
- Tight integration with the Eclipse platform
- Easily create custom trigger scripts or trigger extensions
- Save and edit HTTP message content within the Eclipse environment
- View request and response message details
- Edit messages on the fly with manual triggers