[DERBY-631] Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP Applications

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.1.1.0
• Component/s: Eclipse Plug-in
• Environment: Eclipse RCP
• Assignee: Unassigned
• Reporter: Bernd Lachner
• Created: 17/Oct/05 16:06
• Updated: 29/Aug/07 09:36

Description

I use the Derby Eclipse Core plug-in in an Eclipse RCP Application. If I disable "Unpack the plug-in archive after the installation" in the feature of my RCP Application for the Derby core plug-in, the Derby classes can't be found by "Class.forName("org.apache.derby.jdbc.EmbeddedDriver");" after I deployed the Application and try to start it. It only works when the Derby Core plug-in is unpacked. It seams, the reason for this behaviour is, that the org.apache.derby.core_10.1.1.0.jar contains other jar files (derby.jar, derbyclient.jar, ...) and Eclipse RCP can't handle this. But for example for Java Web Start it would be necessary that the Derby Core plug-in is also packed. Maybe in future versions of the Derby Core plug-in Jars in Jars can be avoided to solve this problem.

Issue Links

• is part of: DERBY-3031 Improve Derby core plugin packaging & structure (solving MANY problems)