-
Notifications
You must be signed in to change notification settings - Fork 313
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
Introduce Spring WS BOM #1290
Comments
Based on the complexity arising and being this late, I'm going to withdraw the BOM from Spring WS |
@gregturn anything I can do to help out with this? |
Thanks @mdeinum. I worked through this slightly modified setup and ran it by a couple teammates for review. This lets us accomplish having the BOM without having to spin up a separate project. |
gregturn
added a commit
that referenced
this issue
Jan 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bom has been configured with a parent:
spring-ws/spring-ws-bom/pom.xml
Lines 7 to 11 in b67a03d
This parent contains dependency management:
spring-ws/pom.xml
Lines 131 to 166 in b67a03d
As a result, the bom's managing the versions of Spring Framework, Spring Security, JUnit, and Jetty. It should only manage the versions of Spring Web Service's own modules.
The text was updated successfully, but these errors were encountered: