Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <26898346.1173314484542.JavaMail.root@brutus>
Date: Wed, 7 Mar 2007 16:41:24 -0800 (PST)
From: "Andrew McIntyre (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2376) Patch available to make .classpath
 entries portable - relative to ECLIPSE_HOME
In-Reply-To: <23165338.1172290745672.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Wow, good eye! I hadn't noticed where these were showing up on the screenshots until you posted the list. Thanks, Aaron, I'll be sure to review the screenshots when you post them.

> 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: DerbyUtils.diff, DerbyUtils.diff
>
>
> 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.