Bug 248583 - [build] Adapt to JDT/Core support for ".." in build path
Summary: [build] Adapt to JDT/Core support for ".." in build path
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 57732
Blocks:
  Show dependency tree
 
Reported: 2008-09-25 10:37 EDT by Jerome Lanneluc CLA
Modified: 2009-03-12 11:43 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2008-09-25 10:37:48 EDT 
I20080923-0800

With the fix for bug 57732, JDT/Core supports ".." in the path to libraries (jar files, class folders). Classpath variables can also contain "..".

JDT/UI need to:
1. make sure that the UI doesn't missbehave if a user edits the .classpath and add such a path
2. add support to let the user enter such a path (Build Path wizard, User Library wizard, etc.)
Comment 1 Jerome Lanneluc CLA 2008-09-25 10:38:14 EDT 
Setting target to M3 as requested by Dani.
Comment 2 Dani Megert CLA 2008-09-25 11:10:05 EDT 
For M3 will solve issue 1. Issue two is time permitting for 3.5.
Comment 3 Dani Megert CLA 2008-10-01 12:49:55 EDT 
OK, I've done step one and found two minor issues:
- bug 249321: IPackagerFragmentRoot#getRawClasspathEntry() returns resolved ".." 
  path. This caused the Remove from Build Path to fail. [fixed]
- the relative roots are rendered resolved and not with ".." i.e. not with raw
  path. I have to check whether we can change this.
Comment 4 Dani Megert CLA 2008-10-02 08:25:36 EDT 
The JDT Core fix for the first issue surfaced another problem on the build path property page: the relative entry is now marked as 'missing'. I've fixed that.

In addition, pressing 'Edit' didn't open for the correct location for relative JARs. I've fixed that too.

Also fixed the label provider.

While testing I found out the using .. together with variables in the .classpath file doesn't work, so this is still an open issue which needs work on the JDT Core side.
Comment 5 Dani Megert CLA 2009-03-12 11:43:59 EDT 
We won't have time to do this for 3.5.