Currently, when we deploy a new GenoViz SDK jar to Nexus, we have to build it locally and then run mvn deploy to release the new artifact to the Nexus repository where we are distributing IGB project artifacts.

The release engineer who does this must configure their local computer to include a release engineer user name and password for accepted by the Nexus site.

However, the version of java used and other aspects may vary. It would be better to use a single environment for building the artifact. Also, it would be nice if this could be done from bitbucket pipelines, which uses the same Docker image as IGB and other Java-based projects.

Let's change how this is done!

For this task:

• Configure the POM for Genoviz SDK and bitbucket pipelines YML to release artifacts to Nexus.

In addition, investigate plugins released by Nexus that deploy artifacts.

See:

• https://www.baeldung.com/maven-release-nexus
• https://stackoverflow.com/questions/28071697/is-it-possible-to-pass-a-password-in-maven-deploy-in-the-command-line

Use google to look for additional tips and examples.

Also, investigate other possible improvements, including formalizing the release process using release branches.

Goal: Make this project as professional as possible to encourage developers to use the library in their projects – and hopefully contribute.