Free images of the 2009 solar eclipse software for linux

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.

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

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.

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.

EasyEclipse packages together the Eclipse IDE and key open source plug-ins. EasyEclipse project is intended to make Eclipse easier to download, install, and use.
Enhancements:
- Three distributions are now available: Expert Java, Plugin Warrior, and C and C++. Not all plugins have been tested.

ant4eclipse project provides a set of Ant tasks that can be used to integrate Eclipse configurations into Ant buildscripts
We all know this situation: the developers of a team are using the Eclipse IDE to code their apps, to compile their apps, to version, to deploy, and to run their apps. No problems so far. But as soon as you want to set up something like a continuous build system which runs outside of Eclipse you also need a build process that is independent of Eclipse. Usually you will use Ant and some other tools to define your automatic build process. Fine. But unfortunately Ant cannot use any of Eclipses configurations, such as classpathes, launcher or team project sets. Although everything has been nicely configured already inside the IDE, it has to be redone in those external Ant build files. And even worse: it has to be reconfigured each time a developer makes changes in Eclipse. As always with redundant data, the challange is to keep Eclipse and Ant configurations in sync. But how about avoiding redundancy in the first place? This is where ant4eclipse comes into play...
The aim of the ant4eclipse project is to avoid (or at least: to reduce) the redundancy of Eclipse and Ant configurations. More precisly: it consists of Ant tasks that are able to read and work with some of Eclipses configuration files. With these tasks youre able to:
- Setup classpathes as defined in Eclipse .classpath-file
- checkout complete workspaces as its possible with the Team Project Set feature of eclipse
- run your Java applications as you have defined them in an Eclipse Launch Configuration
With all these tasks youre able to create a complete automatic build system that starts with checking out all required projects from CVS, builds all projects in the correct order with classpath settings as specified in Eclipse, and to launch your applications as they are specified in Eclipse. And the best of it: if you or someone else changes a configuration in Eclipse, those changes are immediately visible to your buildfiles - without changing one line of code!