db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2376) Patch available to make .classpath entries portable - relative to ECLIPSE_HOME
Date Mon, 23 Apr 2007 20:46:15 GMT

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

Andrew McIntyre commented on DERBY-2376:
----------------------------------------

Hi Bryan,

Sorry, this had dropped off my radar. If you are already looking at the updated files, please
feel free to commit the changes to both trunk and 10.2. I had reviewed the previous versions
and decided that they were ok, until I noticed they were attached without the "grant license
to ASF" JIRA checkbox. Assuming the actual images are the same, then they're +1 to commit
from me as well.

> Patch available 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
>
>         Attachments: completed_javaapp.GIF, completed_javaapp.GIF, create_restaurant.GIF,
create_restaurant.GIF, DERBY-2376.diff, DerbyUtils.diff, DerbyUtils.diff, restaurant_editor.GIF,
restaurant_editor.GIF, restaurant_script.GIF, restaurant_script.GIF, run_javaapp.GIF, run_javaapp.GIF
>
>
> This patch modifies the DerbyUtils class to add variable entries relative to ECLIPSE_HOME
as described in the comments below, 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 derby 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.


Mime
View raw message