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

Bug 327132

Summary: [target] p2 based target does not use local profile when resolving
Product: [Eclipse Project] PDE Reporter: Darin Wright <darin.eclipse>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, jeffmcaffer
Version: 3.7   
Target Milestone: 3.7 M4   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on: 331068    
Bug Blocks:    

Description Darin Wright CLA 2010-10-06 12:01:04 EDT 
I have a target definition file that points to a directory and several p2 repositories. After the initial resolve/download of content, the target will still hit remote repositories and perform a planning operation, rather than using the content of the local profile.

The definition is based on internal IBM repositories (so I won't share in this bug report), but can make it available to committers as required.
Comment 1 Curtis Windatt CLA 2010-10-06 14:53:07 EDT 
I have added a new tracing option for when the IU bundle container looks up data in the profile so we can see if the profile reading is failing and why it failed.

org.eclipse.pde.core/target/profile
Comment 2 Curtis Windatt CLA 2010-10-07 16:44:37 EDT 
There is a problem with the profile resolution when there are multiple p2 repos to load from.  Looks like they may not be sharing the same profile (or they are overwriting the existing profile).
Comment 3 Curtis Windatt CLA 2010-11-04 12:47:07 EDT 
This needs more investigation in M4 as it affects the other target enhancements we are considering.
Comment 4 Curtis Windatt CLA 2010-12-01 15:50:52 EST 
This appears to be working with the current patch on bug 331068
Comment 5 Curtis Windatt CLA 2010-12-02 14:36:37 EST 
Fixed by bug 331068