Free spring ide eclipse 2.0.1 software for linux

Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes.
The Spring Rich Client Project (RCP) is a sub-project of The Spring Framework. Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes. Initial focus is on providing support for Swing applications but a goal of Spring-RCP is to be view agnostic as much as possible.
Spring Rich Client Projects goal is to provide a viable option for developers that need a platform and a best-practices guide for constructing Swing applications quickly.
Specifically, spring-richclient seeks to:
Provide a way to build structured, highly-configurable, GUI-standards-following Swing applications faster by leveraging the Spring Framework.
Foster integration with existing rich-client-related projects where it make sense. For example, jgoodies-forms and TableLayout are two good layout managers. We dont need to develop another one.
Adhere to the principles set forth by the Spring Framework--programming to interfaces; the importance of sound OO design, documentation, and testing.
Main features:
- A command framework that provides centralized configuration of Swing actions and appropriate handler registration based on the current active view. Command configuration, as well as action bar contribution policies (to menus or toolbars), can be defined centrally and externalized in Spring bean defintiions.
- A forms data binding and validation framework, for connecting edits made in your UI controls with your domain model automatically--with as you type feedback.
- Support for multiple window management, page configuration, and view management. The concepts here are inspired by Eclipses perspective/view constructs. Views can be defined in the Spring container, associated with one or more pages, and a default page can be configured to be loaded at startup.
- Common support classes addressing various rich client requirements including: well formed dialogs, wizards, input validation (typing hints and validation results reporting), button bars,internationalization, image/icon caching, progress monitoring, UI threading (classes cleanly promoting responsive UIs), treetable/property sheet, table sorting/high-volume table updates, GUI standards builders/helpers, help/about, etc.
Spring-rich adds value for people needing to develop Swing applications and do so in a way that promotes consistent, well-designed, configurable Swing applications. The spring-rich developers strongly feel the old days of Swing apps not looking native and not being performant or web-accessible are gone with JDK1.4.2 and 1.5 and webstart.
It is our belief the only problem with Swing is that there are a limited number of higher-level abstractions available that assist in making the toolkit simpler and easier to use, and a limited number of design best practices. The goal of spring-richclient is to provide that.
Enhancements:
- [RCP-400] - jgoodies forms not included as spring-rich dependencies
- Regression bug: icons on MessageAreaPane didnt show up

FITpro for Eclipse allows easier creation of FIT tests and suites, more flexible test execution, and more.
Main features:
- Create Fit tests in WYSWIG HTML Editor
- Create suites, ordered collections of Fit tests and sub-suites.
- Execute tests and suites.
- Link from tests to related fixtures.
- Insert Test Template into a Fit test, based on an existing fixture.

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.

PHP Eclipse adds support for PHP, SQL, CSS, HTML and JavaScript to the Eclipse IDE Framework.

The PHPeclipse project aims to create a full featured PHP IDE with PHP, HTML, SQL, Debugger support. The PHPeclipse plugins are based on the Eclipse IDE Framework

Qore Eclipse IDE Plugin software allows you to develop in the Qore Programming Language within Eclipse.
Qore language syntax highlighting:
- code completion
- outline view for edited source
- launch support from within Eclipse (running Qore scripts with output displayed in Eclipse console, qore executable must be installed locally)
- generating of function documentation (alpha stage)

Spindle is a plugin for the Eclipse Platform that provides excellent IDE support for Web apps developed using the Tapestry framework.
Spindle Plugin includes wizards for creating applications and application components. Editors for applications, libraries, pages, components, and templates, all with popup help, syntax completion, and "as you type validation" are included.
A project build process catches and marks almost every runtime Tapestry error before you deploy your application.
Enhancements:
- The documentation has been integrated with context-sensitive key bindings.
- Major bugfixes and feature enhancements.
- Documentation is now available online.

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.