Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327132 - [target] p2 based target does not use local profile when resolving
Summary: [target] p2 based target does not use local profile when resolving
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M4   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 331068
Blocks:
  Show dependency tree
 
Reported: 2010-10-06 12:01 EDT by Darin Wright CLA
Modified: 2010-12-02 14:36 EST (History)
2 users (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 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