Hi Michael, > The main drawbacks with switching to this are: > 1. We'd lose consistency with all of the other Dropwizard module projects, > unless they also changed their versioning strategy. > 2. We'd likely want to maintain a version compatibility matrix in each > module's README.
The idea with the current versioning strategy for (official) Dropwizard modules was to make it very easy for users to see, which version of Dropwizard they were targeting. This of course comes at the cost of not being able to use semantic versioning with the modules themselves, but we thought it might be worth it, especially since we wanted to maintain modules for more than one major/minor version of Dropwizard. The Spring ecosystem is doing it a little differently and is using semantic versioning (more or less) for all sub-projects on their own. This leads, in my humble opinion, to some confusion which versions of Spring Security and Spring Cloud work well with a specific version of Spring Boot. YMMV. ;-) Cheers, Jochen -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-dev/DF94A3EE-12D5-434B-A1CB-43BD6FD3735D%40schalanda.name. For more options, visit https://groups.google.com/d/optout.
