Bugzilla – Full Text Bug Listing
| Summary: | Marketplace should support composite listings | ||
|---|---|---|---|
| Product: | [Technology] MPC | Reporter: | Konstantin Komissarchik <konstantin> |
| Component: | Install | Assignee: | Project Inbox <mpc.install-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mober.at+eclipse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Konstantin Komissarchik
Marketplace can already handle what you call composite listings by adding multiple feature ids to a single marketplace entry. In the marketplace wizard the user has the opportunity to deselect entries for installation once the solution is selected and the user has pressed 'Next'. Per bug 280726 comment # 15 p2 discovery is specifically designed to handle your use case. Please continue this discussion on bug 280726. *** This bug has been marked as a duplicate of bug 280726 *** So... I understand my solution can specify multiple root features to install, but how do I specify multiple repositories to pull from ? See also http://dev.eclipse.org/mhonarc/lists/mpc-dev/msg00296.html > I understand my solution can specify multiple root features to install, but how
> do I specify multiple repositories to pull from ?
>
> See also http://dev.eclipse.org/mhonarc/lists/mpc-dev/msg00296.html
The typical solution is to either mirror the third-party plugins into your repository or to reference the other repo from yours. This would fix the issue you are facing not just for the marketplace listing but for direct install using regular p2 UI or commands.
In a second reading, I see that I didn't fully understand your question. Although, you can still use the aggregate repository approach that I described and then list the aggregate on the marketplace. (In reply to comment #3) > The typical solution is to either mirror the third-party plugins into your > repository or to reference the other repo from yours. I think I understand mirroring though I haven't used it recently; but what I'd prefer here is reference the other repo from mine. How do I do that ? Is it documented anywhere ? I couldn't find any docs for that. I'll just copy part of my mailing list reply here for reference. As Konstantin suggested, the best way for you to go is probably creating a composite repository. There are a couple of things you can do. 1. If you control the main update site or feature(s), you can (and probably should) make sure that all required sites are seeded into the user's site list. To do that you can a) at the feature level add discovery sites: in the feature editor under "Information/Sites to visit" b) at the p2 repository level add repository references. I'm using Buckminster, where a repository is defined through a feature project. There you can just add discovery urls as above and they will end up as repository references in the p2 metadata. Not sure how this works with PDE/build or Tycho. 2. If you don't control these artifacts, you can always just create your own composite repository pointing to the required repositories and use that as your marketplace update site. See here: http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_(new) Many thanks for the input ! This is exactly what I've been looking for. For the records, the concrete implementation of this is tracked here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=402565#c2 |