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.
Submitting M2E marketplace entries
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
- where we can get artifacts from. can either be a p2 or maven repository (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
Extensions that consist of a single OSGi bundle jar or a single lifecycle-mapping-metadata.xml file can be deployed to a publicly accessible Maven repository like https://oss.sonatype.org.
<repositoryUrl/>, artifact <groupId/>, <artifactId/>, <version/> are required and <classifier/> elements are optional
If classifier is provided, it must be "lifecycle-mapping-metadata", in which case the artifact is assumed to be in lifecycle mapping metadata xml descriptor format.
Artifacts without classifier are assumed to be OSGi bundle jar files.
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