Community
Participate
Working Groups
Build Identifier: Helios The org.eclipse.epp.mpc.ui plugin defines both the user interface as well as the default Eclipse marketplace features as well. As a result, any re-use of the marketplace client automatically includes the Eclipse marketplace, whether or not that's desirable. The only way of not consuming the Eclipse marketplace catalog is to copy and paste the UI into a different bundle and not consume the catalog information with it. Can we split up the bundles so that the UI is separate from the standard Eclipse marketplace catalog definition? That way, it would be possible to consume the UI independently from any one catalog. Reproducible: Always
Alex, there has been some work done regarding this issue. Starting with Indigo, there are no predefined catalogs in the MPC plugins anymore. All the catalog information retrieved from a remote catalog service (eg. http://marketplace.eclipse.org/catalogs/api/p). The catalog service has a default hardcoded url to the eclipse marketplace as it was too late in the cycle to make it pluggable but for now, you can still switch to another catalog provider by using the following VM argument -Dorg.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.url=http://some.thing.org/ I'll leave this bug open for now to improve the situation by extracting the default catalog out of the MPC ui bundle and let it be contributed by EPP.
Closing as fixed. We have the discovery since Indigo, and since Luna you can replace the services for both marketplace discovery and communication with discovered marketplaces, which should give you full flexibility.
