Juergen Zimmermann

The according stacktrace is e.g.: ``` The configuration :annotationProcessorCopy was resolved without accessing the project in a safe manner. This may happen when a configuration is resolved from a thread...

Here is pom.xml from com.sun.mail:javax.mail:1.5.3. Line 116 contains ``. ``` com.sun.mail all 1.5.3 4.0.0 com.sun.mail javax.mail jar JavaMail API javax.mail JavaMail(TM) API Design Specification javax.mail javax.mail.*; version=${mail.spec.version}, com.sun.mail.imap; version=${mail.osgiversion}, com.sun.mail.imap.protocol;...

@nstuyvesant supertest@next uses superagent 5.1.0.

Thank you.

@bsideup When I use `-XX:+AllowRedefinitionToAddDeleteMethods` the stacktrace goes away

As expected: issue persists with Gradle 7.5-rc-2

The issue still exists with io.qameta.allure 2.10.0

Gradle 7.5.1: Hopefully not "The same procedure as every year" https://www.youtube.com/watch?v=Nysm_ErwdFE ;-)

@vlsi @baev The upgrade to Gradle 7.6-milestone-1 works fine. Thank you for your efforts!

Please upgrade to 4.3.0 so that "npm audit" doesn't complain about https://github.com/hakimel/reveal.js/pull/3137