Releases

Tasks

1. Update Copyright end year in all files
2. Make a list of changes - check the milestone in github
3. Release jar to Maven Central (See Below)
4. Update readme.md with new current version number
5. Push new JavaDoc to gh-pages branch

Maven Release Process

This guide documents how to create a release of javaparser on The Central Repository.

Prerequisites

1. To be able to release artifacts on on the Central Repository, you must provide PGP signatures for all your artifacts (all files except checksums), and distribute your public key to a key server like http://pgp.mit.edu. Read How to Generate PGP Signatures with Maven for more information.
2. You must be confirmed by Sonatype via an application to upload artifacts to the appropriate coordinates. See the guidelines here. You can see an example application for this project under https://issues.sonatype.org/browse/OSSRH-5465. In our case we use always the following criteria:

• Group Id: com.github.javaparser
• Project URL: https://github.com/javaparser/javaparser
• SCM url: https://github.com/javaparser/javaparser.git

3. Read the Usage Guide to have a clear understanding how to do a release

Stage a Release

First you need to prepare a release before uploading any artifact:

$ mvn release:clean
$ mvn release:prepare

You will be asked how the release version should be named and what name should be used to create a new tag.

Then stage the release:

$ mvn release:perform

Maven will checkout the tag you just prepared before. It will build and deploy the project to OSS staging repository.

Promote a release

To release the uploaded artifacts, open your favorite browser and go to https://oss.sonatype.org/. Sign in and close the corresponding repository. If the validation of the uploads is successful you're allowed to release them (promoting the artifacts to the public).

Something unclear?

Read the Usage Guide in detail, because everything important is described in detail there.

See extended Sonatype Release Guide