Summary: | [buildpath] relative build classpath leading outside of eclipse workspace | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Simon Jefferies <sjefferies> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | daniel_megert, darin.eclipse, dpwegener, eclipse, robert.wenner | ||||
Version: | 3.0 | ||||||
Target Milestone: | 3.5 M3 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Bug Depends on: | 248466 | ||||||
Bug Blocks: | 248583 | ||||||
Attachments: |
|
Description
Simon Jefferies
2004-04-07 09:29:26 EDT
Interesting ideas, but not for 3.0 *** Bug 166572 has been marked as a duplicate of this bug. *** Reopening to consider for 3.5 Will investigate for 3.5M3 Created attachment 113459 [details]
Proposed fix and regression tests
Cannot release until bug 248466 is fixed. Entered bug 248583 for the JDT/UI work. Fix and test released for 3.5M3. Note that one can use this feature by editing the .classpath for now. UI work can be followed in bug 248583. To clarify, note that the ".." is supported for library entries and variable values. A container can also have a library entry with a "..". Other classpath entry paths (such as source entries) cannot have a "..". Seems to work for '..' inside variable path or library path. This doesn't work: <classpathentry kind="var" path="HOME/../../../../java_tools/lib/als.jar"/>. If this is intended, then verified for 3.5M3 using I20081026-2000. (In reply to comment #10) > Seems to work for '..' inside variable path or library path. > This doesn't work: > <classpathentry kind="var" > path="HOME/../../../../java_tools/lib/als.jar"/>. > > If this is intended, then verified for 3.5M3 using I20081026-2000. Yes this is intended. ".." in variable path is not supported. ".." is supported in variable value. Hi, are there any plans to implement relative source paths as well? (In reply to comment #12) > Hi, are there any plans to implement relative source paths as well? > Sorry no plan to support relative source paths. Please enter a separate bug and provide a patch if this is important to you. Although the current status of this bug is Fixed/Verified, I think it should be re-opened because the current implementation has limited use. The lib paths are relative to the workspace location. This makes the feature useless to developers who wish to use relative paths for projects aren't contained in their workspaces. It would be much more useful if the paths were relative to the project. As an example, consider a workspace rooted at /home/user1/workspace. The workspace references a project rooted at /development/component/project1. There is a directory of jars that project1 depends on at /development/component/lib. The logical use for the relative path here would be to define an lib entry in project1 such as <classpathentry kind="lib" path="../lib/some.jar">. The expectation would be that this would reference /development/component/lib/some.jar. However, the current implementation would resolve this to /home/user1/workspace/lib/some.jar. |