[jira] [Commented] (UIMA-2590) Placing the rat plugin into the normal build procedure

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559706#comment-13559706 ] 

Marshall Schor commented on UIMA-2590:
--------------------------------------

There are several use cases to optimize for, in doing the build design.  

* One is "jenkins" - can run a long time, should catch all kinds of issues.  
* Another is developer work, checking fixes, etc. - often repetitive, should run a short time to increase developer productivity.

I would suggest adding another kind of profile - for the jenkins use case - and having the rat plugin run there.  UIMA-AS build has a set of tests, called the "extended tests" (which take a long time to run) which are not normally run for developer work, but which are run during Jenkins builds.
                
> Placing the rat plugin into the normal build procedure
> ------------------------------------------------------
>
>                 Key: UIMA-2590
>                 URL: https://issues.apache.org/jira/browse/UIMA-2590
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Richard Eckart de Castilho
>            Priority: Minor
>
> Currently, the rat Maven plugin is run only in the *apache-release* plugin. How about placing this into the regular build or at least in a separate profile so that Jenkins builds can be made to fail on license problems without running the rest of the release-specific actions?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira