Bug 99350 - [workspace] Can't build a plugin that depends on linked binary plugin
Summary: [workspace] Can't build a plugin that depends on linked binary plugin
Status: RESOLVED DUPLICATE of bug 66177
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-10 09:32 EDT by Tobias Widmer CLA
Modified: 2005-06-11 12:38 EDT (History)
0 users

See Also:


Attachments
MANIFEST.MF and build.properties (880 bytes, application/x-zip-compressed)
2005-06-10 09:33 EDT, Tobias Widmer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
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 ***