Geronimo Eclipse Plugin - Development Roadmap

Need to add support for qualified builds. JIRA 0000
Scripts to update site.xml and publish distributions to the update site. JIRA 0000

Fully support "Run resources from workspace" JIRA 0000
Export Geronimo Plugin wizard JIRA 0000
Remove all dependencies to the WTP Generic Server Framework. JIRA 0000
Full set of deployment plan editors JIRA 0000
Custom source view for deployment plan that provide a fully synchronized non qualified view of a deployment plan. JIRA 0000
Run schema conversion directly from runtime to improve footprint JIRA 0000
Add the Geronimo shared library as an optional part of the runtime classpath container. JIRA 0000

The following are requirements to WTP for function that need to be implemented to improve the Geronimo plugin.

The following are requirements to Geronimo itself in order to implement many of the features listed above.

In order to improve intergation with tooling environments, Geronimo needs to improve its flexibilty in where and how application contents are located at deployment time. An optimal development environment consists of an enviorment in which the deployment processing time is kept to a minimum and users can make code modifications and test them with little or no overhead. An effective way to achieve this is to reduce resource copying and be able to run an entire J2EE application from within a given IDE's project structure. The geronimo runtime needs to be much more adaptable in locating application contents. In this proposal, we will use the Eclipse WTP J2EE project structure as an example showcasing where different types of resources can reside.