[ http://jira.codehaus.org/browse/SUREFIRE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly moved MOJO-1501 to SUREFIRE-609: ------------------------------------------------- Component/s: (was: failsafe) Maven Failsafe Plugin Affects Version/s: (was: failsafe-maven-plugin-2.4.3-alpha-1) 2.4.3 Key: SUREFIRE-609 (was: MOJO-1501) Project: Maven Surefire (was: Mojo) > Failsafe should create workingDirectory if it does not exist > ------------------------------------------------------------ > > Key: SUREFIRE-609 > URL: http://jira.codehaus.org/browse/SUREFIRE-609 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin > Affects Versions: 2.4.3 > Environment: Fedora 11, Maven 2.2.1 > Reporter: Peter Janes > Attachments: failsafe-workingDirectory.patch > > > Failsafe allows the user to set a workingDirectory, e.g. > <workingDirectory>${project.build.directory}/failsafe-working-directory</workingDirectory>, > but if it doesn't exist the integration-test goal reports a > CommandLineException: > [INFO] Error while executing forked tests.; nested exception is > org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: > Working directory "/home/pjanes/failsafe/target/failsafe-working-directory" > does not exist! > The attached patch creates the directory if it doesn't exist. This can also > be worked around by adding an instance of maven-antrun-plugin that invokes > Ant's <mkdir> task, but it seems like overkill and unnecessary > repetition to configure and invoke a completely separate plugin just to > create a directory. > (maven-surefire-plugin doesn't create its workingDirectory either.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira