[MINVOKER-224] Unable to set cloneProjectsTo to null

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0, 3.0.1
• Fix Version/s: 3.1.0
• Assignee: Olivier Lamy
• Reporter: Phillip Webb
• Created: 05/Aug/17 04:49
• Updated: 15/May/18 12:03
• Resolved: 29/Mar/18 03:30

Description

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:

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.

Is it possible to revert this change, or to provide a alternative property to allow cloning to be skipped?

Issue Links

• links to: GitHub Pull Request #2