db-derby-dev mailing list archives

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

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

Bryan Pendleton resolved DERBY-2376.

       Resolution: Fixed
    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Thanks Andrew and Aaron!

I committed the images and HTML files to the trunk as revision 531595.

I then merged both revision 515864 (the DerbyUtils change) and
revision 531595 (the docs change) to the 10.2 trunk using svn merge -r.
The merge was clean and simple, so I committed the change to the
10.2 branch as revision 531597.

Aaron, I think you should assign this Jira issue to yourself, since
you did the development of this change. Thanks for the patch!

> 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:
>         Environment: any with eclipse
>            Reporter: Aaron Tarter
>             Fix For:,
>         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.

View raw message