Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 153311 - Wrong classpath for binary projects with linked content
Summary: Wrong classpath for binary projects with linked content
Status: RESOLVED DUPLICATE of bug 158589
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-09 11:32 EDT by Andrew Niefer CLA
Modified: 2006-09-29 16:25 EDT (History)
1 user (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 Andrew Niefer CLA 2006-08-09 11:32:50 EDT 
During export, for binary projects with linked content, pde/ui provides us with a dev.properties map so that we can find the libraries.

However, when placing libraries on the classpath, the paths are treated as relative to the bundle.  In the case of linked content, this results in an incorrect path:
.../org.eclipse.osgi/eclipse/plugins/org.eclipse.osgi._3.2.100.v2006.jar

We should recognize when we have an absolute path for the library because of dev.properties and leave it as such, or do the proper work to make it relative instead of just appending it.

Note that during a headless build, we will not have the dev.properties and will be unable to located the linked library.  Do we need to worry about this use case?
Comment 1 Andrew Niefer CLA 2006-09-29 16:25:50 EDT 
Brian put a patch to fix this on bug 158589

*** This bug has been marked as a duplicate of 158589 ***