Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Submitting M2E marketplace entries"
| Line 7: | Line 7: | ||
#* name, description and summary (don't ask what's the difference between the last two) | #* name, description and summary (don't ask what's the difference between the last two) | ||
#* license and provider information | #* license and provider information | ||
| − | #* | + | #* p2 repository and installable unit information of the extension (see below) |
#* sample project and steps to see your extension in action | #* sample project and steps to see your extension in action | ||
#* optionally, url of the extension source repository. | #* optionally, url of the extension source repository. | ||
| − | Existing submissions are listed in [http://git.eclipse.org/c/m2e/m2e- | + | Existing submissions are listed in [http://git.eclipse.org/c/m2e/m2e-discovery-catalog.git/tree/org.eclipse.m2e.discovery.oss/connectors.xml this XML descriptor] |
==Maven repositories== | ==Maven repositories== | ||
| − | + | Due to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=346830 bug 346830], support for resolving m2e marketplace catalog entries from Maven repositories has been disabled. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
==P2 repositories== | ==P2 repositories== | ||
For m2e extensions published in p2 repositories we need information about p2 repository url, installable unit id of the feature or bundle to be installed and installable unit id of a bundle that contains lifecycle-mapping-metadata.xml | For m2e extensions published in p2 repositories we need information about p2 repository url, installable unit id of the feature or bundle to be installed and installable unit id of a bundle that contains lifecycle-mapping-metadata.xml | ||
| + | |||
| + | Make sure extension's installable unit contains applicable license information. In practical terms, this means extension must have feature.xml files with <license/> element. | ||
Revision as of 00:40, 24 June 2011
Where to start
- Open a bugreport in m2e bugzilla with "[catalog] your extension name" in the subject.
- In the bugreport please provide the following information about your m2e extension
- name, description and summary (don't ask what's the difference between the last two)
- license and provider information
- p2 repository and installable unit information of the extension (see below)
- sample project and steps to see your extension in action
- optionally, url of the extension source repository.
Existing submissions are listed in this XML descriptor
Maven repositories
Due to bug 346830, support for resolving m2e marketplace catalog entries from Maven repositories has been disabled.
P2 repositories
For m2e extensions published in p2 repositories we need information about p2 repository url, installable unit id of the feature or bundle to be installed and installable unit id of a bundle that contains lifecycle-mapping-metadata.xml
Make sure extension's installable unit contains applicable license information. In practical terms, this means extension must have feature.xml files with <license/> element.