Community
Participate
Working Groups
Build ID: M20090211-1700 Steps To Reproduce: 1. Create a project with some dependent jars. 2. Commit to source control. 3. Open project on Windows. Notice the build paths have to be updated manually. 4. Update them manually and build. 5. Commit changes. 6. Open project on Linux or other. 7. Update to HEAD. 8. Notice it no longer builds. 9. Update manually to proper paths. 10. Build and commit fix. Repeat ad infinitum. More information: Please support relative paths for project jars. Please use relative paths rather than absolute paths as the default.
.classpath files are created by JDT.
Could you please give details? Classpath variables should be used in this case.
Are the jars within the projects?
No. We have several projects and had the jars one level up above those. We now have created a new directory and are using a project with just jars. I think that may be the work-around. We used the project preferences button to "add external jars". That's where I think the path gets set to absolute rather than relative. No big deal I guess.
Yes, if you use external jars, you end up with absolute paths. You could still use a classpath variable pointing to the parent folder.
The classpath variables are made to fix this kind of issues. Is it working for you ?
Closing as WORKSFORME. Classpath variables should be used in this case. If they don't work, please let us know what the problem is.
Verified for 3.6M1