Community
Participate
Working Groups
We're in the process of redoing the p2 target provisioner in PDE. I was excited about the possibility of using a profile to manage some of the target... however, this may be a bad idea after talking to Jeff. He suggested that we look at using the new Mirroring/Slicer functionality in p2 to fetch the artifacts we need. This way, we don't need to spoof a profile like we do currently, and we're able to fetch things like the delta pack. So let's discuss the pros and cons here.
If we use the slicer approach, we will have to make sure that the artifacts are in runnable form too. This may involve running some of the repo2runnable logic.
*** Bug 263294 has been marked as a duplicate of this bug. ***
If we use the Repo2Runnable tool we will have to deal with bug 264267. Either the tool will have to support it or perhaps we can figure out the complete set of IUs to download.
You could also use the PermissiveSlicer class to figure out the list of things that needs to be grabbed and then pass that to the p2ToRunnable task. This is especially doable if you are doing everything in Java
Created attachment 131707 [details] patch Initial draft of IU bundle container. Each bundle container specifies a set of IUs and Repos. An IProfile is maintained for each target definition - collect and install phases are run (no configure phase). The profile is set up with environment & nl properties to get proper OS-specific bundles/fragments installed. Additionally, features are installed.
*** Bug 264119 has been marked as a duplicate of this bug. ***
Released initial code for IUBundleContainer along with tests.
Committed the first set of UI changes. Definitely still needs polish but the new UI will make it easier to test the bundle container.
*** Bug 272498 has been marked as a duplicate of this bug. ***
Darin and I put in several improvements today, both to the UI and to the resolution code. I consider this bug fixed, as it really just needs some polish which we can open new bugs for.