directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <>
Subject Re: PluginManagement / update policy
Date Wed, 03 Sep 2008 15:13:54 GMT
On Wed, Sep 3, 2008 at 11:05 AM, Felix Knecht <> wrote:

> >
> > 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 />
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Too many unapproved licenses: 1625
> See also the rat reports:
> IMO rat cancel the build as long as it finds Unknown licenses.
> Rat reports are only generate for projects using the project/pom version
> 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.

Agreed we should release the project project asap and then focus on the
subprojects as you suggest.

BTW notice that some of those files that RAT complains about are build
byproducts generated by maven in the target directory.  Like for ApacheDS
the unknown licenses for files are things like surefire reports and maven
intermediate files under target.

I wonder if we can tell RAT to ignore what's under the target directory.



View raw message