incubator-oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Woollard (JIRA)" <>
Subject [jira] Commented: (OODT-38) Remove License Test from Build Process
Date Mon, 20 Sep 2010 16:38:38 GMT


David Woollard commented on OODT-38:

Hey guys, Sorry I have not been active on this thread, but, as the creator of this problem/feature,
I figured I should give my two cents.

I wrestled with the same problem RE top level vs subproject and opted for the simple, albeit,
not maven-oriented solution of just declaring the plugin for particular, well-established
sub-projects. At the time that it was incorporated, rat would give a clean bill of health
to the top level build, so someone since my rat commits has added rat to a module that is
not license compliant or added unlicensed files (either way, we should figure that out).

My theory on the subject is as follows: if you get a project license compliant, then you want
to know if you added something and broke compliance. If RAT is only applicable for some sub-projects,
then you will not have to worry about new development until rat is added to that subproject's
build (more work possibly, but also I see it as a natural progression).

I guess I'm fine with a special target, but I also thing that people should realize if they
take an established, vetted component (like filemgr), added some unlicensed code, and try
to build it. For patches, moving away from rat at every build will just mean that the committer/release
manager will need to be very vigilant wrt running a rat audit (not a bad thing).

> Remove License Test from Build Process
> --------------------------------------
>                 Key: OODT-38
>                 URL:
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces
>            Reporter: Paul Ramirez
>            Priority: Minor
>             Fix For: 0.1-incubating
> Currently during the build a failure is caused by a test that counts the number of unapproved
licenses. While it is good to know that there are unapproved licenses it would seem like this
should be something disconnected from the build process. Otherwise on a simple "mvn install"
one runs into the following:
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Too many unapproved licenses: 133
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 23 seconds
> [INFO] Finished at: Sun Sep 19 10:28:29 PDT 2010
> [INFO] Final Memory: 52M/123M
> [INFO] ------------------------------------------------------------------------

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message