Sonatype Nexus Repository 3.69.0 is now available. This release introduces customizable user token expiration, Java 17 support for deployments using PostgreSQL or H2, and multiple improvements to our SAML integration.
See the Sonatype Nexus Repository 3.69.0 Release Notes for full details.
As a Nexus OSS user I’m trying to understand what this means for me. It appears that OrientDB does not support JDK17 and according to this page (Migrating to a New Database) migrating from OrientDB to H2 is considered a Pro feature. So are you saying that Nexus OSS users CANNOT migrate and that we’d have to do a fresh install and lose our existing configs, but obviously support for <JDK17 would naturally go away eventually?
Steve,
I read it that you can still use OSS with JDK up to 11. For now it is not an issue, until JDK11 is still not EOL.
I believe the Sonatype Developers will have to decide on OSS underlying DB or on potential shutdown of the OSS flavor somewhere in future. It may also be that the OrientDB will become at some point JDK17 compliant.
For now - no red flags to stay on OSS / 3.69+, as I see it.