[
https://issues.apache.org/jira/browse/MINVOKER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496609#comment-14496609
]
Christopher Tubbs commented on MINVOKER-190:
--------------------------------------------
I'm using {{<cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo>}}
in my particular use case.
However, that does not solve the problem. The problem occurs because the
*invoked* project (the one cloned) is running plugins which do not recognize
the {{build.log}} file created in that project's root. Ensuring the invoked
project is cloned to the invoking project's target directory only addresses the
issue of confused plugins running on the invoking project, but that's not what
is being described here. What is being described here is plugins running in the
*invoked* project.
> build.log file location causes problems
> ---------------------------------------
>
> Key: MINVOKER-190
> URL: https://issues.apache.org/jira/browse/MINVOKER-190
> Project: Maven Invoker Plugin
> Issue Type: Improvement
> Reporter: Christopher Tubbs
>
> The {{build.log}} file is quite annoying because it is placed in the invoked
> project's source tree by default. It is not configurable, except to disable
> it entirely with the {{noLog}} option.
> This causes issues, such as what is identified in RAT-160, where certain
> plugins behave in unexpectedly bad ways when it appears in the invoked
> project's root.
> Ideally, I'd love for the {{build.log}} file to be created outside of the
> invoked project's source tree entirely. The most sensible, I think, is in the
> invoking project's target/ directory, named uniquely for that invocation.
> Another option is in the invoked project's target directory (which may not
> otherwise exist, so this may not be suitable). A third option is to make the
> location completely configurable, and leave it up to the user to decide where
> it goes.
> The important thing to remember is that not every plugin on an executed
> project can be configured to ignore this file, so it definitely shouldn't be
> created in the invoked project's root by default when there isn't an option
> to put it elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
