"Qulice" Profile for Static Quality Control

Profile qulice can be activated only manually from command line, e.g.:

$ mvn clean install -Pqulice

It runs a number of checks to make sure the quality of the build is acceptable. These plugins are used at the moment to control quality and prevent errors:

• qulice-maven-plugin is a compound static analysis plugin, that pre-configures and executes Checkstyle, PMD, FindBugs, CodeNarc (for Groovy code) and a few other plugins in one bucket. That's why the name of the profile, since this is the biggest tool being executed. It is expected by default that your LICENSE.txt is located in a root directory of every module.
• maven-duplicate-finder-plugin is a filter of duplicate classes and resources in classpath. It is a very useful tool to catch overriding dependencies and exclude them earlier.
• maven-dependency-plugin with its analyze-only goal helps to identify dependencies that are not used, or the ones that are used but not defined.
• xml-maven-plugin is a validator of XML files for "well formedness".

All plugins are bound to the verify Maven phase. All executions are named jcabi-check.