Hi, I have added the license-maven-plugin [1] to the parent and main reactor POM. The goal is to generate overviews of all dependencies and their licenses within the Stanbol code base [2].
When running 'mvn install' the plugin generates a 'DEPENDENCIES-BY-LICENSE' file in META-INF for each JAR. This file lists all dependencies of the artifact grouped by licenses. This file is also generated for the top level reactor POM. By this, we get an overview of all dependencies and their licenses in /target/maven-shared-archive-resources/META-INF/ after running 'mvn install' from the root folder. At the moment there is a large list of dependencies with unknown licenses. To resolve the unknown licenses we have to edit the new src/licenses/THIRD-PARTY.properties file you find in the source folder of each artifact. This file is automatically generated and lists all dependencies with unknown licenses. By adding the license information to these files the problem gets solved. For Stanbol releases we have to know the license of each dependency. So unknown licenses are not allowed. I have configured the RAT profile of Stanbol to raise a build failure if there are any unknown licenses. The RAT profile is activated by 'mvn install -Prat'. This checks for missing license headers in our source files and unknown licenses. Hopefully, this helps us to resolve all license issues before doing a release. [1] http://mojo.codehaus.org/license-maven-plugin/ [2] https://issues.apache.org/jira/browse/STANBOL-493 -- Fabian http://twitter.com/fctwitt
