Open serzhshakur opened 3 years ago
ok, the issue is that you setting allure commandline version (using version.set(allureVersion)
), but not updating allure-java version (allureJavaVersion.set(allureVersion)
).
So the following will work:
allure {
version.set(allureVersion)
adapter {
allureJavaVersion.set(allureVersion)
frameworks {
junit5
}
}
}
since we are using the same version for allure-java and allure report itself it probably makes sense to fix it and make so users only set a single property by default.
@baev , is allureJava
adapter always released together with allure-commandline
?
If that is the case, we could use allureJavaVersion.convention(allure.version)
so allureJavaVersion
is using allure.version
by default.
WDYT?
At the same time, we should probably bump the defaults for allure.version, apsectjVersion, etc.
I believe the issue is fixed in https://github.com/allure-framework/allure-gradle/pull/99
I'm submitting a ...
What is the current behavior?
No reports are generated when using latest Allure version (2.16.1)
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
This can be easily observed using this project Do
Click the link provided by
allureAggregateServe
in the output - no report is served. The report is successfully generated when using Allure version 2.14.0 and below (check the same project onmaster
branch).What is the expected behavior?
Report should be properly generated and viewed while served.
Please tell us about your environment: