Loading
Resolve "Java version used for JTango and all the java ecosystem"
Closes #152
Major upgrades for versions and dependencies:
- Minimum Java 8 -> Java 17
- org.mozilla.rhino 1.7.7.1 -> 1.9.1
- JUnit 4.13.1 -> 6.1.3 (change in package name: junit.junit -> org.junit.jupiter.junit-jupiter. Use
org.junit.junit-bom) - SLF4J-API 2.0.9 -> 2.0.20
- org.zeromq.jeromq 0.5.3 -> 0.6.0
- org.apache.commons.commons-lang3 3.13.0 -> 3.20.0
- org.apache.commons.common-math3 Removed
- org.mockito.mockito-core 4.11.0 -> 5.24.0
- maven-surefire-plugin 3.0.0-M5 -> 3.6.0 (Compatibility issues with JUnit otherwise)
- org.apache.maven.plugins.maven-javadoc-plugin 3.1.1 -> 3.12.0
- maven-deploy.plugin 3.0.0-M1 -> 3.2.0
- org.quartz-scheduler.quartz 2.3.2 -> 2.5.2
- org.databene.contiperf Removed
- ch.qos.logback.logback-classic 1.3.11 -> 1.6.4
- maven-failsafe-plugin 2.22.2 -> 3.6.0 (Compatibility issues with JUnit otherwise)
Important informations:
- We will need to migrate to version v3 of ehcache
- Many refactoring to reduce the number of warnings were done
- When going from JUnit 4 to JUnit 6, org.databene.contiperf was removed and therefore removed a few performance and latency tests done here. The current other alternatives are full fledge benchmarking
- Needless to say, every test was rewritten to match JUnit 6. If you notice any regression or new issue, please file an issue
For the next versions of Java, we will need to fix the following:
The DeviceProxy instances call finalize() just when the garbage collector is about to remove the object from memory. This behavior has been deprecated and removed in Java 18+...
The original purpose of this finalize() call was to unlock the device in the event that the proxy called lock() on a device proxy previously.
The documentation indicates that using AutoCloseable or try-with-resources (try catch clauses for all device proxies...) could be solutions but it might easier to refactor the code to avoid this behavior in the first place.
Edited by Tison Alexandre