Community
Participate
Working Groups
There is a very strange phenomenon when you try to define a relative class path entry in a project. I have inherited a project previously developed in Netbeans where the folder structure looks like this: ProjectRoot ProjectRoot/Libraries # Contains all jars ProjectRoot/ProjectA # Contains .classpath, .project, src etc ProjectRoot/ProjectB # Contains .classpath, .project, src etc If I use ProjectRoot (or a folder above it) as the workspace folder, then I cannot get to jars using relative paths. Let me give an example: If I use Path="Libraries/somelib.jar" in classpath, it looks for the jar in ProjectRoot/ProjectA/Libraries. If I use Path="../Libraries/somelib.jar" it looks for the jar in a folder above the workspace folder. If you have a more complex workspace where ProjectA and ProjectB is not directly under the workspace root, then the problem is even more complex. Expected behaviour: If Path="Lib/x.jar" points to "Lib" subfolder of a project root, then "../Lib" should point to the Lib folder of the direct parent of the project root.
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.
