[
https://issues.apache.org/jira/browse/RAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487701#comment-14487701
]
Christopher Tubbs commented on RAT-160:
---------------------------------------
[~khmarbaise]: as pointed out earlier in the thread (and demonstrated by the
example project provided), the apache-rat-plugin was not configured in the
integration test. Rather, it is inherited by the parent pom.
The issue is independent of the fact that it's an integration test (that just
happens to be the way I was running the invoker plugin). It can occur
*whenever* the maven-invoker-plugin executes a project that has rat in its
build, just like RAT-185 can occur whenever Jenkins executes a project that has
rat in its build.
> Fails to ignore build.log created by maven-invoker-plugin
> ---------------------------------------------------------
>
> Key: RAT-160
> URL: https://issues.apache.org/jira/browse/RAT-160
> Project: Apache Rat
> Issue Type: Bug
> Affects Versions: 0.10
> Reporter: Christopher Tubbs
>
> When using maven-invoker-plugin to run integration-tests for a maven plugin
> project, maven-invoker-plugin creates a build.log file in the basedir for the
> project.
> This may be a bug in maven-invoker-plugin. Perhaps it'd be better to put this
> file in its build directory, rather than its basedir. Regardless, the
> apache-rat-plugin should ignore this build.log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
