-
Notifications
You must be signed in to change notification settings - Fork 31
Allow possibility to specify the Working Directory #27
Comments
possibility to set the Working directory. Also, fixed the CachedArtifactTest because it was platform dependent.
The default working directory is ${project.build.testOutputDirectory} as said in the issue klieber#27 and the integration tests projects have other structure.
@mdaloia thanks for your contribution. I think the |
"workingDirectory" as requested by @klieber at klieber#27
Given that the default value for the parameter "workingDirectory" was reverted to "${project.basedir}" as requested in klieber#27, the changes on the integration tests settings are redundant. This reverts commit 62a5736.
IT because it seems that the test "exec-with-command-line-options" sometimes it doesn't find the text to assert. Part of klieber#27
@klieber I updated the pull request but it seems that Travis-CI is having some misbehavior with the IT tests, mostly with My environment is:
This is a log excerpt:
|
Currently when the plugin is executed from a project the working directory is the project base dir. [1]
The phantomjs command executes using this directory and there isn't option to change it.
Add a
workingDirectory
optional parameter to theexec
goal to customize it.I think that given that this goal it is bound by default to the lifecycle phase
test
the default working directory must be the${project.build.testOutputDirectory}
with the posibility to change it. [2][1]
PhantomJsProcessBuilder.start()
usesProcessBuilder
and looking at the JavaDoc ofjava.lang.ProcessBuilder.directory()
we find this:[2]
This will break backward compatibility but to get the same behavior of version < 0.5 you can set
<workingDirectory>${project.basedir}</workingDirectory>
inside the section of this plugin.The text was updated successfully, but these errors were encountered: