Vladimir Sitnikov
Vladimir Sitnikov
I believe this is fixed with https://github.com/allure-framework/allure-gradle/pull/61 Please feel free to try it and provide feedback.
What are your "strange errors" exactly? Here's a sample for report aggregation: https://github.com/allure-framework/allure-gradle/tree/master/allure-plugin/src/it/report-multi Here's the documentation: https://github.com/allure-framework/allure-gradle#aggregating-results-from-multiple-projects
@ootaken , thanks for the isssue. How are you doing? I did not know why JUnit 5 data was not collected, and thanks to the issue I know it :)...
Resolved in #61
This PR leverages Gradle dependency resolution for `allure-commandline` download: https://github.com/allure-framework/allure-gradle/pull/61 So both dependency cahcing and dependency verification would work. Please feel free to try it and provide feedback
Implemented in #61
@pshakhov , are you sure `add(project.dependencies.create("org.aspectj:aspectjweaver` is evaluated early? The `add` in question is located within `defaultDependencies` which means it happens only when configuration is resolved. I think `allure-gradle` does...
This PR adds Gradle 5.0...7.0 with a streamlined DSL: https://github.com/allure-framework/allure-gradle/pull/61 See the new DSL at https://github.com/vlsi/allure-gradle/tree/facelift#basic-usage Please feel free to try it and provide feedback
We'd probably want using Gradle Java Toolchains: https://docs.gradle.org/current/userguide/toolchains.html#sec:plugins