Status of Morphia 3.0 and Java 17 compatibility #3380
jodyfanning
started this conversation in
General
Replies: 1 comment
-
2.4.x passes all the tests against Java 17 and 21, for what it's worth. I
don't know of any issues regarding those java versions. As for 3.0, it's
slowly moving along. I've been focusing on automated upgrades scripts via
openrewrite to assist in upgrading and so that's stalled progress in other
areas but those scripts are coming along quite nicely and I have a pretty
good feel for what needs to be done there. Having those scripts in place
gives me some wiggle room to tidy the API a bit more. You can see the
current state of the upgrades by following along here:
https://github.com/MorphiaOrg/morphia-upgrade-testing. But 3.0 will
require Java 17 so it's good you're thinking about that now. I'm heading
for some conference travel but I'm hoping to pick up the pace once I'm
back.
…On Thu, Jan 30, 2025 at 5:30 AM Jody Fanning ***@***.***> wrote:
I have a project that is currently in the process of migrating to Java 17
(from 11), and which is using Morphia for many of the collections it
contains. Morphia 2.x not being Java 17 compatible is a bit of a blocker
for that. So now the main question is do we bite the bullet and migrate to
using the native driver POJO support, or do we wait until 3.0 would come
with Java 17 support? The project likely doesn't use many of the advanced
features of Mophia, but of course the move to native driver POJO support
means writing codecs for many of the enum types that we use.
So news on what the current state of 3.0 is, or any other thoughts /
experiences with Java 17 and MongoDB in general.
—
Reply to this email directly, view it on GitHub
<#3380>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABPTTMLDVGKZN5UYUU3JOL2NH5LRAVCNFSM6AAAAABWE5AGLOVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXHA4TENRSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a project that is currently in the process of migrating to Java 17 (from 11), and which is using Morphia for many of the collections it contains. Morphia 2.x not being Java 17 compatible is a bit of a blocker for that. So now the main question is do we bite the bullet and migrate to using the native driver POJO support, or do we wait until 3.0 would come with Java 17 support? The project likely doesn't use many of the advanced features of Mophia, but of course the move to native driver POJO support means writing codecs for many of the enum types that we use.
So news on what the current state of 3.0 is, or any other thoughts / experiences with Java 17 and MongoDB in general.
Beta Was this translation helpful? Give feedback.
All reactions