Closed MoonlightSentinel closed 3 years ago
Thanks for pointing that out - I will investigate.
Okay, somehow the Gradle .module
files got published, too. The POM for 2.8 contains <packaging>pom</packaging>
, which is wrong. I fixed that, will now investigate why the module is published, too. Or will fix the module file. Damn you gradle.
I just released version 2.9, this should be on Maven Central tomorrow. I hope this fixes this bug, will test tomorrow.
I had to restructure the gradle build, the dependency tree now looks like this:
\--- de.mkammerer:argon2-jvm:2.9
\--- de.mkammerer:argon2-jvm-nolibs:2.9
\--- net.java.dev.jna:jna:5.6.0
this should be transparent to users of the library (everything should work as usual).
Works now on my example project. @MoonlightSentinel Could you please re-test that?
Both the example mentioned above as well as my real project(s) work now. Thanks!
The library cannot be found on the classpath after upgrading to version 2.8 (previous versions compile without error).
Example project:
build.gradle
settings.gradle
App.java:
Errors: