Common parser functionality for static code analysis tools on continuous integration servers to read reports and send the data to Artemis
-
Make sure you have a Sonatype JIRA account. Store the credentials in the settings.xml in the m2 home folder
-
Make sure you have a valid GPG certificate (follow the instructions on https://central.sonatype.org/publish/requirements/gpg)
-
Store the used key in your Maven settings.xml file, usually placed in ~/.m2: https://central.sonatype.org/publish/publish-maven
-
Run
export GPG_TTY=$(tty)
-
Run
mvn clean deploy -P release
This should create the jar file, sources, javadoc and the pom file. All files should also have an additional signed *.asc file. You might find the files in your m2 home folder. -
Verify the artifact and release it to Maven Central:
- Open https://oss.sonatype.org/#stagingRepositories,
close
the repository to start the validation - As soon as the validation has finished successfully,
release
the artifact. - After some time, the new release should be available on https://search.maven.org/artifact/de.tum.in.ase/static-code-analysis-parser
- You can also check https://packages.atlassian.com/maven-external/de/tum/in/ase/static-code-analysis-parser
- Open https://oss.sonatype.org/#stagingRepositories,