You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can depend on DiscordSRV as a gradle dependency and use a modern version of jetbrains annotations that supports TYPE_USE annotations.
Actual behavior
Since 1.26.1, jetbrains annotations in getting included in the released jar, but it's a newer version, so it's fine.
Since 1.27.0, an ancient Java 5 version is included, which lacks TYPE_USE. This breaks usages like this:
publicvoidf(byte@NotNull [] message) {}
This snippet won't compile if DiscordSRV is included as a dependency in my gradle project.
Steps to reproduce
Open up the jar file of 1.27.0 and note the existence of the org/jetbrains/annotations folders. Use javap on any class (like "NotNull.class") and note that the major version is 49, corresponding to java 5. Also note the lack of TYPE_USE in the bytecode.
There is no reason to include annotations in the release jar, they don't do anything after compilation.
Also, your issue tracker is not built for handling build or dependency errors.
The text was updated successfully, but these errors were encountered:
Expected behavior
I can depend on DiscordSRV as a gradle dependency and use a modern version of jetbrains annotations that supports TYPE_USE annotations.
Actual behavior
Since 1.26.1, jetbrains annotations in getting included in the released jar, but it's a newer version, so it's fine.
Since 1.27.0, an ancient Java 5 version is included, which lacks TYPE_USE. This breaks usages like this:
This snippet won't compile if DiscordSRV is included as a dependency in my gradle project.
Steps to reproduce
Open up the jar file of 1.27.0 and note the existence of the org/jetbrains/annotations folders. Use javap on any class (like "NotNull.class") and note that the major version is 49, corresponding to java 5. Also note the lack of TYPE_USE in the bytecode.
Server software and version
not relevant
Checks
Anything else
There is no reason to include annotations in the release jar, they don't do anything after compilation.
Also, your issue tracker is not built for handling build or dependency errors.
The text was updated successfully, but these errors were encountered: