Plans for Dropwizard 3

Including Logback’s alpha versions, the dependencies could now be updated to the jakarta namespace.

Should we - as most other Jakarta EE components - support both the javax and the jakarta namespace and therefore build Dropwizard 3, or should we postpone the upgrade?

[joschi]

@dropwizard/committers @zUniQueX What do you think about the following roadmap?

• Dropwizard 2.2.x with Jetty 10.x (and Java 11 baseline)
• Dropwizard 3.x with Jetty 11.x (and Java 11 baseline and Jakarta EE namespace)

While Dropwizard 2.2.x formally is breaking semantic versioning (because of the change of the language baseline from Java 8 to 11), it would still work largely as before and it might give users a little nudge to upgrade to Java 11 in production. 😉

Other than that I don’t think Jetty 10 will break a lot of things which are officially supported by Dropwizard (see also https://webtide.com/jetty-10-and-11-have-arrived/) and thus the upgrade from Dropwizard 2.1.x to 2.2.x should cause only minor upgrade pain - if at all when people are already on Java 11.

[pstackle]

Dropwizard 2.2.x with Jetty 10.x (and Java 11 baseline)

@joschi Why not just call this v3 and be explicit about the change? I’m not sure that we gain much by trying to sell it as a minor update. Based on the work that @zUniQueX has done, it sounds like there are at least a handful of Jetty 10 changes that we’d have to reason about. By upgrading to Jetty 10 + Java 11 as a major Dropwizard version, it seems to me that it better communicates the magnitude of the change.