| Summary: | Questionable paths being generated by PDE Build since 3.7M7 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Chris Aniszczyk <caniszczyk> | ||||
| Component: | Build | Assignee: | pde-build-inbox <pde-build-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | aniefer | ||||
| Version: | 4.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Chris Aniszczyk
Created attachment 195795 [details]
post 3.7M7 build.xml
Chris, I think this is just because the binary jars in the target are somewhere on disk far away from the buildDirectory. I think that you might have seen this before the nested jar change. We've always tried to do relative paths to help support something like the releng source build where Kim zips up the generated scripts for someone else to run. Going from /home/zx/eclipse/eb/org.eclipse.linuxtools.eclipse-build/eclipse-build/build/eclipse-3.7.0-I20110512-2000-src to /user/lib/eclipse is pretty far for a relative path and in this case an absolute path would probably be better. We could perhaps check if the relativization went all the way to the root and then just use absolute path if it did. Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix. |