[
https://issues.apache.org/jira/browse/JENA-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2077:
--------------------------------
Description:
Run Apache RAT checks only when running maven in the top directory.
This means:
RAT checks will be done for the whole project in one single plugin run at the
start.
Previously, it ran on entering the module so a RAT failure could occur late in
the build.
Does not run when maven executed in a module during development.
It makes it possible to switch to using a RAT exclusions file, rather than
inline in the plugin configuration. It is hard (not possible?) to name the
exclusions file to work for both parent and module use.
was:
Run Apache RAT checks from only when running maven in the top directory.
This means:
RAT checks will be done for the whole project in one single plugin run at the
start.
Previously, it ran on entering the module so a RAT failure could occur late in
the build.
Does not run when maven executed in a module during development.
It makes it possible to switch to using a RAT exclusions file, rather than
inline in the plugin configuration. It is hard (not possible?) to name the
exclusions file to work for both parent and module use.
> Run RAT from the top directory only.
> ------------------------------------
>
> Key: JENA-2077
> URL: https://issues.apache.org/jira/browse/JENA-2077
> Project: Apache Jena
> Issue Type: Improvement
> Components: Build
> Affects Versions: Jena 3.17.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 4.0.0
>
>
> Run Apache RAT checks only when running maven in the top directory.
> This means:
> RAT checks will be done for the whole project in one single plugin run at the
> start.
> Previously, it ran on entering the module so a RAT failure could occur late
> in the build.
> Does not run when maven executed in a module during development.
> It makes it possible to switch to using a RAT exclusions file, rather than
> inline in the plugin configuration. It is hard (not possible?) to name the
> exclusions file to work for both parent and module use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
