-
-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serenity-cli: when using the --destination flag, default destination folder is created anyway #2454
Comments
Hi @wakaleo , I retested this with the |
Inactive issues are closed automatically from time to time. |
Happy to review a pull request for this. The line you reference is just the default value, I think. |
Hi @wakaleo , I'm very sorry, but I was not able to build the project. Therefore I'm not able do debug or contribute, but I think I found a hint. I removed permission from the Line 63 in 8568a70
Seems there are default values set at other places, as well, not just in the cli?
|
Thanks for noticing that. At some point I will try to investigate. |
To be clear, this is really no big issue for me, at least not for now. I would understand if you decide to not to fix and close this issue. I think we can reopen it at any time. |
Hi,
it seems, that the default destination directory
./target/site/serenity
is created, despite of having passed different--source
and--destination
paths.serenity-core/serenity-cli/src/main/java/net/serenitybdd/cli/Serenity.java
Line 28 in c9a11f6
I attach two *.json test results as they could be produced with https://github.com/serenity-js/full-stack-acceptance-testing-demo. result.zip
./result
java -jar serenity-cli-2.4.24.jar --source ./result --destination ./report
./report
folder./target/site/serenity
as wellShortly discussed this issue with @jan-molak here.
This issue has low impact for me at the moment, but may cause problems in environments, where you have no write access to this path for reasons.
The text was updated successfully, but these errors were encountered: