Description Igor Fedorenko 2011-09-27 20:55:38 EDT

m2e discovery catalog items that use m2e 1.1 specific APIs cannot be installed and used with m2e 1.0. Catalog items that define m2e version range as [1.0,1.1) cannot be installed with m2e 1.1. We need to make sure both m2e 1.0 and 1.1 only offer installation of compatible items.

Unfortunately p2 discovery does not validate if catalog item can or cannot be successfully installed, so we need to public 1.0 and 1.1 catalogs under different URLs.

Here is a rough plan

* each connectors.xml entry will carry list of compatible m2e versions, i.e. 1.0, 1.1 and so on. Entry can be compatible with one or more m2e versions.
* m2e 1.0 catalog will continue to be published to https://repository.sonatype.org/content/repositories/forge-sites/m2e-discovery-catalog/
* m2e 1.1 catalog will be published to new https://repository.sonatype.org/content/repositories/forge-sites/m2e-discovery-catalog-1.1/
* update catalog publishing plugin to generate both 1.0 and 1.1 catalogs from the same connectors.xml
* for bonus points, validate that each catalog entry can be installed with declared versions of m2e.