|
|
| Line 5: |
Line 5: |
| | ==Submitting new m2e marketplace entries== | | ==Submitting new m2e marketplace entries== |
| | | | |
| − | # Open a bugreport in [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e m2e bugzilla] with "[catalog] your extension name" in the subject.
| + | "m2e marketplace" is a misleading and confusing term. It is called "discovery catalog" in m2e ui. |
| − | # In the bugreport please provide the following information about your m2e extension. Use [http://git.eclipse.org/c/m2e/m2e-discovery-catalog.git/tree/org.eclipse.m2e.discovery.oss/connectors.xml this XML descriptor format], in other words, we'd like to be able to paste provided entry information directly to the descriptor. For updates to existing entries, please provide diffs we can apply with patch or git.
| + | |
| − | #* 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 [http://git.eclipse.org/c/m2e/m2e-discovery-catalog.git/tree/org.eclipse.m2e.discovery.oss/connectors.xml this XML descriptor]
| + | See [[Submitting M2E discovery entries]] for a brief explanation how to submit new or modify existing entries. |
| − | | + | |
| − | ==Updating existing marketplace entries==
| + | |
| − | | + | |
| − | # Clone git.eclipse.org/c/m2e/m2e-discovery-catalog.git
| + | |
| − | # Make desired changes to org.eclipse.m2e.discovery.oss/connectors.xml
| + | |
| − | # Verify your changes by running "mvn clean install" from the root of the repository
| + | |
| − | # Commit your changes
| + | |
| − | # Generate patch using "git format-patch HEAD^" command
| + | |
| − | # Open new bugreport in m2e bugzilla with "[catalog] your extension name" in the subject and attach the patch to the bugzilla
| + | |
| − | | + | |
| − | ==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==
| + | |
| − | | + | |
| − | 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.
| + | |
| − | | + | |
| − | It is assumed that contents of provided p2 repository will not change in the future unless corresponding m2e marketplace catalog entry is removed or amended.
| + | |
"m2e marketplace" is a misleading and confusing term. It is called "discovery catalog" in m2e ui.
