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

Aaron Tarter commented on DERBY-2376:
-------------------------------------

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"/> 

> Patch avaialble to make .classpath entries portable - relative to ECLIPSE_HOME
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-2376
>                 URL: https://issues.apache.org/jira/browse/DERBY-2376
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Eclipse Plug-in
>    Affects Versions: 10.2.2.0
>         Environment: any with eclipse
>            Reporter: Aaron Tarter
>             Fix For: 10.2.2.1
>
>
> 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.

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