> > Yes I think we already do this for ApacheDS project when the -Prelease > flag is present to trigger the release profile. If we do not then we > should - we should do what you suggest TLP wide.
Ok. I added the rat:check to the -Prelease. Please note that ATM almost none of the projects can be released because of this. E.g. apacheds: mvn clean install -Prelease [INFO] Scanning for projects... [INFO] Reactor build order: <snip /> [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Too many unapproved licenses: 1625 See also the rat reports: http://vm094.oxylos.org/projects/apacheds/rat-report.html http://vm094.oxylos.org/projects/daemon/rat-report.html http://vm094.oxylos.org/projects/shared/rat-report.html http://vm094.oxylos.org/projects/studio/rat-report.html http://vm094.oxylos.org/projects/studio-plugin/rat-report.html IMO rat cancel the build as long as it finds Unknown licenses. Rat reports are only generate for projects using the project/pom version 12-SNAPSHOT. If we want to go ahead with the release we should update now the project/pom.xml, release it, set in all sub projects (if exists) the parent pom to the relased version (12) and then continue with fixing whatever is needed for the release of the subproject. Felix
