Improve Derby core plugin packaging & structure (solving MANY problems)

There are some problems with the current packaging of the core plugin. Since eclipse 3.3 it is highly recommended to package plugins as "jar packages". Additionally all current eclipse plugins come jar'd and signed!

I propose the following packaging:

• Split plugin into several plugins. One plugin per old jar included – this way a plugin is a JAR and not a plugin-folder with n jars in it
• These plugins need their requirements and exports set right thus separating db-server from client-libraries and so on (reduce size)
• Add a feature to get "full" derby support with branding (better representation is never a bad idea)

Why?

• Conform with eclipse. No more plugin-folders. No update-manager hassles. No RCP developer problems
• When jar's are signed webstarting automatically works.
• Feature for better representation & update manager support (preferred installation method nowadays)
• much lighter footprint

How?

• "inject" MANIFEST.MF into existing single jar's, renaming them to conform "eclipse-style" with version indicator (as multiple plugin versions are supported)
• provide download zip with "feature" and "plugins" directories where the feature/plugins live in

This solves the following long-standing bugs:
http://issues.apache.org/jira/browse/DERBY-2175
http://issues.apache.org/jira/browse/DERBY-631

...and includes...:
http://issues.apache.org/jira/browse/DERBY-1488

I always wanted to report this, because currently I'm repackaging every derby update to keep my software running...so is this feasible??
Thank you & Greetings from Vienna!