incubator-oodt-commits mailing list archives

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


Paul Ramirez commented on OODT-38:

Sounds like its a question at this point if we want rat to be configured by default on the
build of a sub module. I would vote yes given that it would still come down to whether or
not they pass the "-Daudit=true" flag when building. We currently have a pretty standard set
of sub modules and those should evolve slowly over time so it seems acceptable that they would
blow up on an audit test moving forward unless otherwise configured. 

I did notice that the rat plugin is currently configured at the core level in the reporting
section; besides being included in sub modules. Not sure if this will end up being redundant
no matter the choice that is taken to move this forward. Anyone know what having it in the
reporting section will do? Does this stall the reporting process if rat doesn't like stuff?

I might be able to get the best of both worlds by adding another level of indirection but
it seems like overkill at this point. Essentially, the activation of the audit could be a
based on runAudit=${audit} in the core pom. In each of the submodule poms if they wanted to
avoid audit they could simple specify in their pom properties audit=false. By default the
core would set the audit=true and I believe that would give us everything we wanted. I'd have
to try this out but I think it would work. Thoughts? 

> 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