Refresh plugin and update cargo to latest compatible version 1.10.13 #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I upgraded the plugin and the Jenkins baseline to recent versions so I could finally bump the used cargo version from 1.7.6 (July 2019) to 1.10.13 (April 2024). Newer versions of Cargo produced a lot of UpperBoundaryExceptions from the maven-enforcer-plugin. Motivation for the upgrade itself was bugfix codehaus-cargo/cargo@44e8b2c which solves re-deployment issues when using ROOT.war files with Tomcat manager.
Testing done
Executed manual deploy test to make sure that CARGO-1563 fixes the problem when re-deploying ROOT.war files with Tomcat manager.
Submitter checklist