You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Susan Cline (JIRA)" <de...@db.apache.org> on 2005/10/18 18:59:47 UTC
[jira] Commented: (DERBY-631) Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP Applications
[ http://issues.apache.org/jira/browse/DERBY-631?page=comments#action_12332375 ]
Susan Cline commented on DERBY-631:
-----------------------------------
I'm a little confused by this report. I haven't built an RCP application, so maybe I am missing something. You mentioned the jar file called org.apache.derby.core_10.1.1.0.jar, is this something that is created when you build the RCP application?
The packaging of the derby core plug-in presently is as a zip file which contains derby.jar, derbyclient.jar, derbynet.jar, derbytools.jar and a plugin.xml
What happens if you:
Unzip the derby core plug-in zip file and leave checked the 'Unpack the plug-in archive after the installation' (however it sounds like this might cause you a problem, can you explain why?)
I believe when building an RCP application you can include an entire directory instead of a jar file when referring to a plug-in? If so, would this work for you?
You mentioned Java Web Start requires the Derby core plug-in be packed. Does this means it needs a zip file or a jar file? What is contained in this file?
If so, is the solution to your problem to create a plug-in that only contains all of the classes of derby.jar in a jar file with a plugin.xml?
Please let me know if I have missed the point. Also, for plug-in providers that package their plug-ins as jar files do these jar files only contain *.class files and the plugin.xml, or do they package it another way?
Your last comment has me confused as well: 'Maybe in future versions of the Derby Core plug-in Jars in Jars can be avoided...' , since we do not package the plug-ins this way, unless you are referring to a zip file being the same thing as a jar file.
> Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP Applications
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-631
> URL: http://issues.apache.org/jira/browse/DERBY-631
> Project: Derby
> Type: Improvement
> Versions: 10.1.1.0
> Environment: Eclipse RCP
> Reporter: Bernd Lachner
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira