[
https://issues.apache.org/jira/browse/MINVOKER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417765#comment-16417765
]
Robert Scholte commented on MINVOKER-224:
-----------------------------------------
Hmm, I don't like the idea that we introduce just another new parameter, which
would result in a chain of parameters to match. MINVOKER-219 is best practice
for Maven plugins, so how about to only set {{cloneProjectsTo}} when the
{{"maven-plugin".equals( project.getPackaging() )}}
> Unable to set cloneProjectsTo to null
> -------------------------------------
>
> Key: MINVOKER-224
> URL: https://issues.apache.org/jira/browse/MINVOKER-224
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Phillip Webb
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.2
>
>
> [MINVOKER-219|https://issues.apache.org/jira/browse/MINVOKER-219] changed the
> default value of {{cloneProjectsTo}} to {{target/its}}. This change
> unfortunately now makes it impossible to have a {{null}} value, meaning that
> in-place invocation is no longer supported. From the Javadoc:
> {quote}Directory to which projects should be cloned prior to execution. If
> set to null, each integration test will be run in the directory in which the
> corresponding IT POM was found. In this case, you most likely want to
> configure your SCM to ignore target and build.log in the test's base
> directory.{quote}
> Is it possible to revert this change, or to provide a alternative property to
> allow cloning to be skipped?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
