Versions Compared

Old Version 13

changes.mady.by.user Norbert Kalmár

Saved on

compared with

New Version 14

changes.mady.by.user Norbert Kalmár

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Deploy to the Maven Repository.
    This is done using apache-release profile, coming from the apache parent pom. This will also sign your artifacts if your settings.xml is configured as mentioned above.
    The following command copies all artifacts to a temporary staging Apache mvn repository in open state:

    Code Block
    mvn deploy -DskipTests -Papache-release


  • Make the release candidate available

    You can check the artifacts you just uploaded in the Apache’s Nexus at repository.apache.org using your Apache ID. Click 'Staging Repositories' and look for a new ZooKeeper repository with a status of 'Open'. Check that all the artifacts and pom files are available. As long as this is in open state, you can re-upload your files. Or just use 'Drop' on the staging repo.

    If it checks out, close the repo using the 'Close' button. The repository must be closed before a public URL to it becomes available. It may take a few minutes for the repository to close. Once complete you’ll see a public URL to the repository in the Nexus UI. You may also receive an email with the URL. Provide the URL to the temporary staging repository in the email that announces the release candidate.

    When the release vote concludes successfully, return here and click the 'Release' button to release the artifacts to central. The release process will automatically drop and delete the staging repository.

  • In Jira, close issues resolved in the release. Disable mail notifications for this bulk change.