maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MINVOKER-224) Unable to set cloneProjectsTo to null
Date Mon, 02 Oct 2017 06:59:00 GMT

     [ https://issues.apache.org/jira/browse/MINVOKER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephane Nicoll reassigned MINVOKER-224:
----------------------------------------

             Assignee: Robert Scholte
    Affects Version/s: 3.0.1
        Fix Version/s: 3.0.2

> 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
>             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
(v6.4.14#64029)

Mime
View raw message