Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MicroProfile/Maven"
(Created page with "The Maven repositories are located under the [https://github.com/eclipse Eclipse Foundation] Github organization, which can be filtered to show the MicroProfile specific repos...") |
(Explained which and how we use Maven repositories) |
||
| Line 1: | Line 1: | ||
| − | + | = Releases repository = | |
| + | |||
| + | For releases, including milestone and candidate releases, the '''Maven Central repository''' is used. There's a common Jenkins job [https://ci.eclipse.org/microprofile/job/MicroProfile%20Releases/ MicroProfile Releases] to release any MicroProfile feature. | ||
| + | |||
| + | After a release is uploaded from Jenkins but before a release is published in Maven Central, usually a manual approval is required in [https://oss.sonatype.org/#stagingRepositories Sonatype Nexus]. Every committer is eligible to have access to the Sonatype Nexus with permission for the org.eclipse.microprofile artifact group prefix. If you are a committer and don't have access, do the following steps: | ||
| + | |||
| + | <ol> | ||
| + | <li> | ||
| + | Register yourself in the [https://issues.sonatype.org public Sonatype Jira] to get an account for both Sonatype Jira and Nexus | ||
| + | </li> | ||
| + | <li> | ||
| + | Create an issue to request access to the org.eclipse.microprofile artifact group prefix and mention that you're a committer to the MicroProfile project. Asa reference, here's the [https://issues.sonatype.org/browse/OSSRH-32787 original Jira for the group prefix]. Link your new Jira issue to the original for reference. | ||
| + | </li> | ||
| + | </ol> | ||
| + | |||
| + | == Eclipse releases repository == | ||
| + | |||
| + | The [https://repo.eclipse.org/content/repositories/microprofile-snapshots Eclipse MicroProfile releases repository] is also available but no longer used since we use the Maven Central repository instead. Sometimes non-final versions like milestones or candidate releases were deployed to this repository instead of Maven Central. This apprach is considered obsolete now and all non-snapshot releases should be published to Maven Central. | ||
| + | |||
| + | = Snapshot repository = | ||
| + | |||
| + | For daily snapshots, the [https://repo.eclipse.org/content/repositories/microprofile-snapshots/ Eclipse MicroProfile snapshot repository] is used. Jenkins snapshot jobs are set to deploy to this repository automatically. | ||
| + | |||
| + | All the artifacts are automatically accessible through the global [https://repo.eclipse.org/content/repositories/snapshots/ Eclipse snapshot repository]. You can add it to maven configuration with the following snippet. As the url, you can also use https://repo.eclipse.org/content/repositories/microprofile-snapshots/ to limit the scope only to MicroProfile artifacts. | ||
| + | |||
| + | <pre> | ||
| + | <repositories> | ||
| + | <repository> | ||
| + | <id>eclipse.microprofile</id> | ||
| + | <name>Eclipse MicroProfile Repository</name> | ||
| + | <url>https://repo.eclipse.org/content/repositories/snapshots/</url> | ||
| + | <releases> | ||
| + | <enabled>false</enabled> | ||
| + | </releases> | ||
| + | <snapshots> | ||
| + | <enabled>true</enabled> | ||
| + | </snapshots> | ||
| + | </repository> | ||
| + | </repositories> | ||
| + | </pre> | ||
Revision as of 21:13, 11 November 2017
Releases repository
For releases, including milestone and candidate releases, the Maven Central repository is used. There's a common Jenkins job MicroProfile Releases to release any MicroProfile feature.
After a release is uploaded from Jenkins but before a release is published in Maven Central, usually a manual approval is required in Sonatype Nexus. Every committer is eligible to have access to the Sonatype Nexus with permission for the org.eclipse.microprofile artifact group prefix. If you are a committer and don't have access, do the following steps:
- Register yourself in the public Sonatype Jira to get an account for both Sonatype Jira and Nexus
- Create an issue to request access to the org.eclipse.microprofile artifact group prefix and mention that you're a committer to the MicroProfile project. Asa reference, here's the original Jira for the group prefix. Link your new Jira issue to the original for reference.
Eclipse releases repository
The Eclipse MicroProfile releases repository is also available but no longer used since we use the Maven Central repository instead. Sometimes non-final versions like milestones or candidate releases were deployed to this repository instead of Maven Central. This apprach is considered obsolete now and all non-snapshot releases should be published to Maven Central.
Snapshot repository
For daily snapshots, the Eclipse MicroProfile snapshot repository is used. Jenkins snapshot jobs are set to deploy to this repository automatically.
All the artifacts are automatically accessible through the global Eclipse snapshot repository. You can add it to maven configuration with the following snippet. As the url, you can also use https://repo.eclipse.org/content/repositories/microprofile-snapshots/ to limit the scope only to MicroProfile artifacts.
<repositories>
<repository>
<id>eclipse.microprofile</id>
<name>Eclipse MicroProfile Repository</name>
<url>https://repo.eclipse.org/content/repositories/snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>