Ignoring Aspectj version in allureAspectjWeaverAgent and allure extension without explicit implementation

[allure-framework]

Ignoring Aspectj version in allureAspectjWeaverAgent and allure extension without explicit implementation

[CristianGM]

Can you try with 2.11.2 I think I changed that behavior.

Previously aspectJ was configured too early and none of the values of the extension were set yet.
In my case we had disabled aspectJ in our buildscripts for ages...but until now it was ignored, it's just now when it was actually disabled and we have seen we actually need it.

[vlsi]

@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 not resolve the configuration at the configuration time, so afterEvaluate is not really needed

Would you please provide Gradle Build Scan or a sample project that reproduces the issue?