| 2020-03-12 11:10:51 |
Frederic Bregier <frederic.bregier@waarp.fr> |
README.md v a5ab58755abbded4d8d1ceaa92955cf8e198fb3e
pom.xml v a5ab58755abbded4d8d1ceaa92955cf8e198fb3e
v1.0.2 upgrade dependencies
Note that only V2.X of Vitam are supported.
V3 of Vitam has broken upgrade path:
- Java 11 is mandatory (while a lot of Java 8 are still out there and that community is not moving as much to Java 11 due to performance and bug issues)
In Waarp, we decide to stay on Java 8 compatibility path. Even Waarp itself is compatible with Java 6 for old platforms, but we did upgrade dependencies for Vitam up to Java 8 considering Vitam installation implies Java 8 at least. However Java 11 is not a good path right now.
- V3 of Vitam clients have broken API usage compared to V2.X (API are the same but behaviors are not): Show stopper!
We try to keep as much as possible compatibility in upgrade path. But here, even if we do not include Vitam Jars (preserving choice of Java 8 or Java 11), the result is that the same code using V2 is working while using V3 is no more working while no compilation error appears.
Broken upgrade path on Vitam side.
Therefore, Waarp-Vitam will not support Vitam V3 until one of the following:
- Vitam correct the V3 version
- Client ask to support excplicitely V3 of Vitam, implying 2 separate branch of the very same code, therefore more effort |
