Skip to content

fix: Adding a managed Maven dependency throws exception if it exists in same or higher version #779

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

Conversation

fabapp2
Copy link
Contributor

@fabapp2 fabapp2 commented Apr 27, 2023

A better and more generic approach must be found.
A Spring baseline version should be defined and updated.
This would be the target version for JEE migration for example.
So after migrating from a JEE application, it should be on the expected Spring version to allow upgrading from there.

@fabapp2 fabapp2 added the type: bug Something isn't working label Apr 27, 2023
@fabapp2 fabapp2 added this to the v0.14.0 milestone Apr 27, 2023
@fabapp2 fabapp2 self-assigned this Apr 27, 2023
@fabapp2 fabapp2 force-pushed the 453-apply-initialize-spring-boot-migration-on-a-boot-application-might-downgrade-boot-version branch from 77c2157 to ad98c4f Compare April 28, 2023 12:24
@fabapp2 fabapp2 merged commit b1d73c1 into main Apr 29, 2023
@fabapp2 fabapp2 deleted the 453-apply-initialize-spring-boot-migration-on-a-boot-application-might-downgrade-boot-version branch April 29, 2023 19:26
fabapp2 added a commit that referenced this pull request May 26, 2023
…in same or higher version (#779)

* format: Fix copyright header
* dep: Bumped spring-asciidoctor-backends to 0.0.5
* dep: Removed Spring release repository after brown out
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Apply initialize-spring-boot-migration on a Boot application might downgrade Boot version
1 participant