Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341571 - PDE fails to build (import not found) when using P2 repositories in target platform
Summary: PDE fails to build (import not found) when using P2 repositories in target pl...
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-01 00:19 EDT by Bryan Hunt CLA
Modified: 2018-12-03 09:12 EST (History)
1 user (show)

See Also:


Attachments
source bundles and target definition (134.83 KB, application/zip)
2011-04-01 00:19 EDT, Bryan Hunt CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Hunt CLA 2011-04-01 00:19:22 EDT
Created attachment 192334 [details]
source bundles and target definition

I'm developing with Eclipse 3.7M6.  When I set up my target platform to include all P2 repositories, my source will not build.  I get import not found errors.

If I build with Tycho using exactly the same P2 repositories for my target platform, the source builds just fine.

The P2 repositories that are giving me problems are ones that I built myself from source and exported using PDE as a deployable feature including repository metadata and a category.xml.

The attached code should be everything needed to reproduce the problem.  It contains two target platform definitions:  MongoBad.target is set up to use only P2 repositories which will not build, and  Mongo.target is set up to get the two repositories I built from the filesystem instead of a web server which builds just fine.
Comment 1 Bryan Hunt CLA 2011-04-01 01:39:20 EDT
I just discovered a workaround by pure accident.  When a feature is created, "Unpack the plug-in archive after the installation" is checked by default.  If I uncheck this option, then PDE will build just fine using all P2 repositories.

I've re-deployed the repositories I built, so you won't be able to reproduce with the attached source and target definition.  If you need them to reproduce the problem, I can make the old ones available.
Comment 2 Lars Vogel CLA 2018-12-03 09:11:16 EST
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.
Comment 3 Lars Vogel CLA 2018-12-03 09:12:38 EST
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.