[
https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Tarter updated DERBY-1931:
--------------------------------
Attachment: DerbyUtils.diff
This patch modifies the DerbyUtils class to add variable entries relative to
ECLIPSE_HOME as described in the comments above, so that eclipse projects with
Derby Nature can be committed to an SCM without causing build path errors. I
did not think any of the functional tests were applicable to this ui action, so
I manually tested the code by trying the following:
1) Adding Derby Nature to a java project
2) Starting and stopping a database with the derby nature
3) Removing the Derby Nature from a java project
The code modification is only required on the add and not on the remove since
the current remove looks for any entry that ends with the correct JAR names.
> 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
> Reporter: Nick Efford
> Priority: Minor
> Attachments: DerbyUtils.diff
>
>
> 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.
