Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 99350

Summary: [workspace] Can't build a plugin that depends on linked binary plugin
Product: [Eclipse Project] PDE Reporter: Tobias Widmer <tobias_widmer>
Component: BuildAssignee: pde-build-inbox <pde-build-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:
Attachments:
Description Flags
MANIFEST.MF and build.properties none

Description Tobias Widmer CLA 2005-06-10 09:32:15 EDT 
I20050610-0010:

Cannot export plugin-project anymore using "Export - Deployable plugins and 
fragments"

-> During the full build, the builder fails to resolve any type which is not 
contained in the JRE libraries

Attaching the MANIFEST.MF and build.properties
Comment 1 Tobias Widmer CLA 2005-06-10 09:33:20 EDT 
Created attachment 22797 [details]
MANIFEST.MF and build.properties
Comment 2 Pascal Rapicault CLA 2005-06-10 09:43:52 EDT 
what do you have in your workspace?
Comment 3 Tobias Widmer CLA 2005-06-10 09:56:22 EDT 
I have all Eclipse SDK plugins imported as linked binary projects, except for 
JDT UI/Core, JDT JUnit, JDT JUnit Runtime plus a few test projects and 
performance test plugins.

The I have this plugin-project whose manifest and build file I attached. The 
workspace builds fine and the plugin in question runs fine in the runtime 
workbench. It only has dependencies to imported Eclipse plugins.

It may have something to do with the manifest (the manifest-bundle version is 
2).
Comment 4 Pascal Rapicault CLA 2005-06-11 12:38:08 EDT 
Closing as dup. 
Even though it is not precisely the same case, it is the same underlying pb: pde build is not link aware.

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