Bug 249449 - [buildpath] ".." not supported in variable extension
Summary: [buildpath] ".." not supported in variable extension
Status: VERIFIED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 4.14 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: readme
Depends on:
Blocks:
 
Reported: 2008-10-02 05:27 EDT by Jerome Lanneluc CLA
Modified: 2019-10-10 02:21 EDT (History)
2 users (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-10-02 05:27:10 EDT 
I20080930-0921

If you add a variable classpath entry in the .classpath file with an extension that starts with "..", the variable is not resolved and you get build path problem reported.

E.g. assuming that junit-4.0.jar is a sibbling of the workspace and adding the following in the .classpath:
  <classpathentry kind="var" path="ECLIPSE_HOME/../junit-4.0.jar"/>
results in a build path problem
Comment 1 Jerome Lanneluc CLA 2008-10-02 09:25:05 EDT 
The problem comes from the fact that we use org.eclipse.core.runtime.Path to represent a classpath variable + its extension. However Path(String) is specified for valid system path. "ECLIPSE_HOME/../junit-4.0.jar" is not a valid system path.

Classpath variables support need to be redesigned to not rely on IPath.
Comment 2 Jerome Lanneluc CLA 2008-10-02 09:25:50 EDT 
For 3.5, we will add this limitation in the readme.
Comment 3 Eclipse Genie CLA 2019-09-03 04:16:42 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Jay Arthanareeswaran CLA 2019-09-09 00:06:55 EDT 
This is still relevant, but I don't expect this to be fixed any time soon. Better close as WONTFIX and move on.
Comment 5 Jay Arthanareeswaran CLA 2019-10-10 02:21:52 EDT 
Verified for 4.14 M1