[
https://issues.apache.org/jira/browse/RAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487716#comment-14487716
]
Christopher Tubbs commented on RAT-160:
---------------------------------------
[~joc...@apache.org]: I don't know about other cases, but in my case, I
wouldn't want to configure an exception in the parent POM... because I don't
expect any build.log files which don't have license headers to show up in my
modules. For my case, I only expect it to occur in my maven-invoker-plugin
executed builds which some of my modules do during testing.
The best workaround I've found so far (short of telling maven-invoker-plugin
not to create a build.log file) is to create a profile which configures rat to
exclude build.log, and activate this profile only when maven-invoker-plugin
executes the 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)
