db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Lachner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-631) Derby Eclipse plug-in shouldn't use Jar packages in the plugin for better usage in RCP Applications
Date Mon, 17 Oct 2005 07:07:45 GMT
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


Mime
View raw message