Hi Siraj, Thanks for sharing your experience! I'll keep that in mind.
On Tuesday, May 26, 2020 at 8:47:23 AM UTC-7, siraj wrote: > > We had to pin to 1.3.3 until 2.0 because whatever came after 1.3.3 broke > something so we had to roll back everything. > We are now on 2.0 and have been on it for a 2-3 months. > > > On Tuesday, May 26, 2020 at 12:41:41 AM UTC-5, Jingjing Duan 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/d8070764-f17d-46fc-85e0-f49ed87c196e%40googlegroups.com.
