[jira] [Commented] (MINVOKER-224) Unable to set cloneProjectsTo to null

["Tomer Cohen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MINVOKER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475719#comment-16475719 ] 

Tomer Cohen commented on MINVOKER-224:
--------------------------------------

[~olamy] Is there an ETA for when the version (which I see right now is stamped as 3.1.0) is to be released? Thanks!

> 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.0, 3.0.1
>            Reporter: Phillip Webb
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Major
>             Fix For: 3.1.0
>
>
> [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)