[
https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475491
]
Aaron Tarter commented on DERBY-1931:
-------------------------------------
I agree that the current behavior of adding four derby lib entries with
absolute path references to the .classpath is problematic. It prevents easy
sharing through an SCM repository like SVN or CVS, since the references are not
relative (i.e. portable). The solution suggested above would be to use an
eclipse IClasspathContainer (like the JRE System Library). Define a container
in the plugin that loads the derby jars and then just add that container to the
.classpath when the user clicks "Add Derby Nature". Another simpler, but
perhaps less pretty, approach is to modify the "Add Derby Nature" popup action
to add var entries relative to the ECLIPSE_HOME variable. So, in this case
they would still appear as non-collapsable individual entries, but at least
they would be portable. The entries in the .classpath would then be:
<classpathentry kind="var"
path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derby.jar"/>
<classpathentry kind="var"
path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbyclient.jar"/>
<classpathentry kind="var"
path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbynet.jar"/>
<classpathentry kind="var"
path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbytools.jar"/>
> 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
>
> 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.
