You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Reference issue from allure2: allure-framework/allure2#1271
To summarize, when using the report goal for a directory that has a space somewhere in the full path, the whole path gets recreated at the current directory with a " directory between. I have discussed why this is happening in the issue ref with a potential fix.
i.e. running mvn allure:report with defaults in a directory like /project workspace/ would produce a report path of /project workspace/"/project workspace/target/site/allure-maven-plugin"/
Expected behavior
Report goal handles spaces in the path for generating the report
Additional context
I've laid out a potential solution in the original issue ref -- changing the "handleQuotes" bool from true to false here resolved the issue when testing locally with unix-like and Windows OS's using the main report versions.
I can PR this fix. Let me know if that might cause anything else to break, but I can rerun the int tests too just in case.
The text was updated successfully, but these errors were encountered:
Describe the bug
Reference issue from allure2: allure-framework/allure2#1271
To summarize, when using the report goal for a directory that has a space somewhere in the full path, the whole path gets recreated at the current directory with a
"
directory between. I have discussed why this is happening in the issue ref with a potential fix.i.e. running
mvn allure:report
with defaults in a directory like/project workspace/
would produce a report path of/project workspace/"/project workspace/target/site/allure-maven-plugin"/
Expected behavior
Report goal handles spaces in the path for generating the report
Additional context
I've laid out a potential solution in the original issue ref -- changing the "handleQuotes" bool from true to false here resolved the issue when testing locally with unix-like and Windows OS's using the main report versions.
I can PR this fix. Let me know if that might cause anything else to break, but I can rerun the int tests too just in case.
The text was updated successfully, but these errors were encountered: