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 "Dyre Tjeldvoll (JIRA)" <ji...@apache.org> on 2007/10/04 19:31:51 UTC

[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a single library in Package Explorer

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

Dyre Tjeldvoll updated DERBY-1931:
----------------------------------

    Derby Info:   (was: [Patch Available])

> 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.