Open czp13 opened 1 year ago
Workaround for executing integration tests is to add at least 5.12.0
(first version where the Memory.close()
method is added) version to the
<dependencyManagement>
...
<dependency>
<groupId>net.java.dev.jna</groupId>
<artifactId>jna</artifactId>
<version>5.12.0</version>
</dependency>
</dependencies>
</dependencyManagement>
We need to discover who is bringing in the 5.8.0 version of jna
@mcollovati Oh I had the same problem, based on the gradle dependency output I would say this is based on the quarkus bom
net.java.dev.jna:jna:5.8.0 -> 5.13.0
\--- io.quarkus.platform:quarkus-bom:3.0.3.Final
\--- project :core
\--- project :core (*)
https://repo1.maven.org/maven2/io/quarkus/quarkus-bom/3.0.3.Final/quarkus-bom-3.0.3.Final.pom
Good catch @ErrorProne, thanks!
Maybe:
quarkus platform
as this is in license-checker
as a transitive dependency. pom.xml
.Note for gradle users, this should fix it:
configurations.all {
resolutionStrategy {
// Required (at least on mac) to force the JNA version so license checking works
force("net.java.dev.jna:jna:5.13.0")
}
}
In a maven project, moving the vaadin bom declaration before the quarkus bom, should fix the issue
Executing tests with:
mvn clean install
(independent of adding the Vaadin version like:-Dvaadin.flow.version=23.3-SNAPSHOT
)This will generate this exception:
It is not happening on Windows, but on Mac, because it has different code execution chain and eventually this will fail:
Potential root case is the transitive maven dependency handling (
5.8.0
is used rather than5.13.0
)