-
Bug
-
Resolution: Done
-
Medium
-
Casablanca Release
-
None
fix for the issue in oparent that started on 20th Oct
upgrade from 5.0.9 across https://git.onap.org/oparent/tree/dependencies/pom.xml#n68
to fix 20181111 CLM issue in oparent "C*-20*-157..56 maven org.springframework : spring-web : 5.0.9.RELEASE spring-web-5.0.9.RELEASE.jarOpen"
https://gerrit.onap.org/r/#/c/72396/
Test
built oparent locally - and updated my root pom.xml to use 1.2.2-SNAPSHOT (master)
see screencap - spring-web is not 5.1.2 not 5.0.9
Team, I am getting a managed version 5.1.2 override because of the oparent definitions under 5.0.9 when inheriting from oparent
this is blocking a full change to spring 5.1.2 downstream
blocks for example
https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/logging-analytics/477be399bd514382be0f7d1e18785e0d
- blocks
-
LOG-616 POMBA: Address CLM critical issues by M4/RC2 - 6 High across all projects
- Closed
-
LOG-834 Logging/POMBA CLM: fix/address/red-flag LA tomcat-embed-core 8.5.32 now orange
- Closed
-
LOG-837 Logging/POMBA CLM: fix/address/red-flag spring-mvc-5.1.2 pulls in spring-web-5.0.9
- Closed
-
TSC-50 oparent CLM status must be managed daily to not block downstream project CLM work - for 20+ days
- Closed
- links to