Prepare release v1.0

[dizzzz]

• use mvn release plugin
• update to v1.0.0
• uploade to public repo

[adamretter]

@dizzzz as you are using the parent https://github.com/eXist-db/exist-apps-parent most of the release stuff is already setup for you.

1. You will need to apply to be added to the groupId org.exist-db for Maven Central, to do that the instructions are here: https://central.sonatype.org/pages/ossrh-guide.html#create-a-ticket-with-sonatype. I am already managing the groupId - so mention that in the ticket, and they will message me and I can approve it.

2. Ensure that you have GnuPG installed, and that you have a key which has been distributed to a public key server, which you can use for signing the artifacts. The actual signing will be done automatically, you just need a functioning and valid key, see - https://central.sonatype.org/pages/working-with-pgp-signatures.html. I can cross-sign your key if need be...

After you are approved by Sonatype and have your PGP key, you can simply run:

$ cd jfreechart
$ mvn clean
$ git status

Make sure everything is committed, and pushed and that you are on your main branch.

Then you can simply run:

$ mvn release:prepare

This will give you some menu prompts and ask you questions about the version number you want to release, the name of the tag to use, and the next development version number (which should be a x.y.z-SNAPSHOT, where x.y.z is greater than the version number you used for release).

$ mvn release:perform

This will take care of bumping all the version numbers appropriately, signing your artifacts with PGP (it will prompt for the pass-phrase of your PGP key), doing all the git tagging and pushing, and uploading a copy of your XAR to the staging server for the Maven Central repository.

Once that is done you will find the xar in target/.

If you also want to release it to Maven Central, you can also visit: https://oss.sonatype.org/ and after logging in you will find it in the Staging Repositories. If you follow this guide, it shows you how to release it to Maven Central, where it will then appear after the next sync window (typically 2 hours) - https://central.sonatype.org/pages/releasing-the-deployment.html