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] Commented: (DERBY-1931) Derby JAR files should be grouped as a single library in Package Explorer
Date Mon, 08 Oct 2007 12:50:50 GMT

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

Aaron Tarter commented on DERBY-1931:
-------------------------------------

I checked out the trunk and verified that the patch was applied correctly.  I was able to
compile, run, add Derby nature, remove Derby nature, start, and stop a database server.

> 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: 10.1.3.1, 10.2.2.0, 10.3.1.4
>            Reporter: Nick Efford
>            Assignee: Aaron Tarter
>            Priority: Minor
>         Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java,
screenshot-1.jpg
>
>
> 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.


Mime
View raw message