db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Tarter (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a single library in Package Explorer
Date Tue, 21 Aug 2007 04:45:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Aaron Tarter updated DERBY-1931:

    Attachment: DerbyClasspathContainerInitializer.java

This patch provides an IClasspathContainer implementation so that all of the derby jars are
contained under a single classpath entry.  This allows system portability and simplifies the
classpath management.  The method is better than the patch provided as part of 2376, since
that method will fail for cases where users install their plug-ins in non-default Eclipse
installation locations.

Besides the diff there are two new files to be added that are included as attachments:


> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>                 Key: DERBY-1931
>                 URL: https://issues.apache.org/jira/browse/DERBY-1931
>             Project: Derby
>          Issue Type: Improvement
>          Components: Eclipse Plug-in
>    Affects Versions:,
>            Reporter: Nick Efford
>            Priority: Minor
>         Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java,
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files
appear individually in the Package Explorer View.   It would be neater if they were grouped
as a single library called "Apache Derby Library", in the same way that the JARs distributed
with a Java run-time environment appear as "JRE System Library".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message