Since it's neccessary to launch all the JUnit tests often, it should be possible with a single klick. For now, one action per project (12+) is needed. The dependencies (classpath, ...) lives in Eclipse Launch Configurations. This depends an Eclipse Plug-in to launch it in the development environment.
The new plugin starts in a new project org.nomadpim.ide_, to migrate the ide project into that plugin & rename it later.
Logged In: YES
user_id=1601903
Originator: YES
The plug-in provides a new popup menu action "Run JUnit Launch Configurations"
to many available menus of the Eclipse workspace. It's intended to use in the
development environment and offers the possibility to run every configuration
that will launch a JUnit test. The scheduled operation is monitored and
cancelable in the Progress view. The launched tests are monitored by the JUnit
and Console views. The results can be gathered in the History of the JUnit view.
It's mostly generated by the "New Plug-in Project" wizard of Eclipse 3.3.0 PDE.
Additionally concepts:
* Platform Plug-in Developer Guide > Reference > Other reference information >
Message Bundles (Eclipse 3 NLS mechanism used)
* Platform Plug-in Developer Guide > Reference > Other reference information >
Eclipse platform API rules of engagement ("internal" package fragments used)
* JDT Plug-in Developer Guide > Programmer's Guide > JDT Debug > Running a Java
program (the second approach)
* Platform Plug-in Developer Guide > Programmer's Guide > JFace UI framework
Long-running operations (usage of a Job and the IProgressMonitor)
Logged In: YES
user_id=1601903
Originator: YES
To migrate the HeaderAndPackageMaintenance, a pop-up menu should be provided for projects, packages and Java sources selected in the Package Explorer. The action should allow multiselections and recurse into containers. The maintenance should be configurable and extendible.