jqassistant/jqa-uber-parent

jQAssistant Ueber Parent

The jQAssistant Ueber Parent is the root parent POM of all other jQAssistant projects.

It is used only to specify properties common for all other jQAssistant projects.

jqa-uber-parent's Issues

Remove snapshot repository declaration from pom.xml

When executing jQA within a Maven build then the following messages are logged to the console:

[INFO] Downloading from sonatype-nexus-snapshots: https://oss.sonatype.org/content/repositories/snapshots/com/google/guava/guava/maven-metadata.xml
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/maven-metadata.xml
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/maven-metadata.xml (4.5 kB at 13 kB/s)

This is probably related to the declaration of the Sonatype OSS repository for downloading snapshots. This practice is considered as an anti-pattern and should therefore be removed from our pom.xml files.

Ensure that no SNAPSHOT artifacts will be part of a release

Ensure that no SNAPSHOT artifacts will be part of a release. Integrate the Maven Enforcer Plugin in the profile release of jQAssistant.

Use Github Actions to provide a simple CI/CD Buildchain

As core developer of jQAssistant, I want this project to be build on various plattforms with different JDK versions on each commit, so that I know if the change done my the commit does not break the build and the software is fully functional.

The following acceptance criterias must be met:

• mvn -DskipTests -Djqassistant.skip clean install must pass
• mvn -Djqassistant.skip clean install must pass
• mvn -P IT clean install must pass
• mvn -DskipTests -Djqassistant.skip=false clean install must pass