1.0.6 is long enough ago (>3 years) that I don’t have good anecdotal memory of what might have been broken. Dependabot thinks Dropwizard’s semver is generally pretty good (98% https://dependabot.com/compatibility-score/?dependency-name=io.dropwizard%3Adropwizard-core&package-manager=maven&version-scheme=semver https://dependabot.com/compatibility-score/?dependency-name=io.dropwizard%3Adropwizard-core&package-manager=maven&version-scheme=semver), but it doesn’t have much information from version to version (especially not 1.0.6 -> 1.3.23).
Do you have continuous integration and (if so) how much do you feel you can trust it? I suspect a fair number of things will turn up relatively early during compilation. While I don’t think many (if any) Dropwizard interfaces have changed from 1.0 to 1.3, it’s possible that a shared dependency may not have fared as well. If you also have tests that start your application up (e.g. https://www.dropwizard.io/en/release-1.3.x/manual/testing.html#integration-testing) then you may pick up changes around configurations, reflection-based code (including META-INF style services). My gut says it’s very feasible. But if I were in your position I’d put together a few carefully placed integration tests prior to the upgrade to help detect the more subtle ways things might break. Ryan On Mon, May 25, 2020 at 10:41 PM Jingjing Duan <[email protected]> wrote: > Hi Folks, > > How feasible is it to upgrade from DW 1.0.6 to 1.3.23? In other words, how > backward-compatible are DW 1.X series? Does DW roughly follow semantic > versioning? > > Long story, we have a pretty large monorepo for backend Java service(100s > of them) built on top of DW and it's been running on 1.0.6 for a few years > now. One big reason that pushes us to upgrade now is that many services > want to bring up newer versions of external libraries and often times they > run into trouble. Take "jackson" for example, a lot services want to > consume newer versions of jackson but DW 1.0.6 only works with jackson up > to certain versions. There might be a hard version conflict of jackson. > > This can also prevent feature development. A service may want to use some > shiny, new ML library and if that library only works with latest "guava", > they may not be able to do so because newer versions of guava may not work > with DW 1.0.6. > > Has anyone had experience upgrading an old 1.X version to the latest 1.X? > Mind sharing? Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dropwizard-user/4ec822f0-6775-40b8-8b13-ccc9c3cab507%40googlegroups.com > <https://groups.google.com/d/msgid/dropwizard-user/4ec822f0-6775-40b8-8b13-ccc9c3cab507%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-user/CAFVYhL-9d1%3D%2BGLp6L1sGH2KfRa-1vsbaC6VVBuyki0B0OTVoww%40mail.gmail.com.
