jqassistant/jqa-own-constraints

Hosts various configurations to verify jQAssistant itself.

jQAssistant Aggregator Repository

jQAssistant has been splitted into multiple repositories to allow more flexible releases.

Note	Want to raise an issue? If possible try to go to the affected repository. If not, please raise it in our Idea Hub.

Want to get started? Here are some links to help you:

• Get Started

• 101 Tutorials

• The jQAssistant Manual

If you have questions related to jQAssistant please get in touch with us via the jQAssistant forum or Stackoverflow.

The table below lists the repositories jQAssistant is made of.

Table 1. List of jQAssistant repositories

BOM	https://github.com/jqassistant/jqa-bom
Commandline Distribution	https://github.com/jqassistant/jqa-commandline-tool
Core Framework	https://github.com/jqassistant/jqa-core-framework
Java Plugin	https://github.com/jqassistant/jqa-java-plugin
JSON Plugin	https://github.com/jqassistant/jqa-json-plugin
Maven 3 Plugin	https://github.com/jqassistant/jqa-maven3-plugin
JUnit Plugin	https://github.com/jqassistant/jqa-junit-plugin
Neo4j Backend	https://github.com/jqassistant/jqa-neo4j-backend
Plugin for Apache Maven	https://github.com/jqassistant/jqa-maven-plugin
XML Plugin	https://github.com/jqassistant/jqa-xml-plugin
YAML 2 Plugin	https://github.com/jqassistant/jqa-yaml2-plugin

Tip

For convenience reasons the repositories are aggregated as sub-modules in this Git repository. You can clone it using git clone --recursive https://github.com/jQAssistant/jQAssistant.git. Once checked out you might need to run git submodule update --remote to update to the latest commits of the sub-modules.

jqa-own-constraints's Issues

Reenable the rule jqa-legal:license:exists

The rule jqa-legal:license:exists ensures that a file called LICENSE exists in the root folder of each jQA related project.

With the release of jQAssistant 1.3.0 this rule started to fail for many projects of jQA as the scan process finds now many occurrences of such a file. It seems so, that the scan results now also contains LICENSE files found in some Jar files.

This needs more time to investigate. As a shorttime solution I disabled the rule for now.

Define a rule to ensure the presence of a version number

Define a rule to ensure the presence of a version number in the parent POM of each project.

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

Ensure via a contraint the the default Github Action CI workflow exists

As the maintainer of jQA, I want to ensure that each subproject of jQA uses out standard Github Action workflow for Continuous Integration, so that it is guaranteed that we perform a build and all tests on every push to the blessed repository.

Define a rule to ensure that SCM information are present

Define a rule to ensure that SCM information are present

Define a rule to ensure the correct information on the organisation

Define a rule to ensure the correct information on the organisation behind a jQAssistant project.

Constraint for Maven compiler settings

The latest 1.3 release accidentially contains java classes compiled for Java 8 instead of the officially suppported Java 7:

• JSON plugin
• Maven 3 plugin

A constraint should verify the Maven settings.