-
-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings thrown in 1.15.5 during Serenity Cucumber Tests Initialisation #1721
Comments
These classes carry optional dependencies to JNA. Since the latest version, Byte Buddy contains Multi-Release versions of its class files, but the optional dependencies have always been there. Could you find out how these tools issue those warnings? |
Do the full stack traces help at all?
and
What's interesting is that the first one says It seems Serenity/Cucumber/JUnit fires off several searchers to try to determine the step definitions:
It does seem to be something to do with the Multi-Release release. |
There are classes in Byte Buddy that implement the Ideally, however, I think that this is something the class path scanner handles. I would not understand how a library like Spring Boot would be handled which includes a massive amount of optional dependencies. |
When upgrading from 1.15.4 to 1.15.5 some warnings are now thrown during Serenity Test Runs:
and
Downgrading to 1.15.4 makes these warnings disappear.
The builds are run in a container using Azul Java and Ubuntu Minimal as the base.
The text was updated successfully, but these errors were encountered: