-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider avoiding feature version in spring boot starter name #459
Milestone
Comments
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
…upgrade to latest spring boot version
ebussieres
added a commit
that referenced
this issue
Aug 8, 2019
Gonna be changed in next release. Thanks |
ebussieres
added a commit
that referenced
this issue
Aug 19, 2019
…upgrade to latest spring boot version (#461) Signed-off-by: Eric Bussieres <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've seen users in the community building 3rd party starters struggling how to prepare the migration to Spring Boot 2 and one way to handle both Spring Boot 1.x and 2.x for the same version was to create a separate starter with Spring Boot 2 in its name.
Spring Boot 1.x is now EOL so I suggest dropping support for it and use the opportunity to remove the second starter. In the future, I'd suggest applying this naming recommendation.
The text was updated successfully, but these errors were encountered: