-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Fix mvnup compatibility: jar-plugin 3.4.2, exec-plugin submodule coverage, toolchain warning #13059
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
Open
gnodet
wants to merge
5
commits into
apache:master
Choose a base branch
from
gnodet:fix/mvnup-compat-issues
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
bea123f
Fix mvnup compatibility issues: jar-plugin target, exec-plugin submod…
gnodet d19e12d
Address review findings: fix Files.walk resource leak and verify warning
gnodet 700038a
Fix property-based plugin version resolution across multi-module proj…
gnodet 63c472c
Fix spurious warning when property already at target version
gnodet 05c3a06
Fix mvnup regressions from compat test run on maven-4.0.x-mvnup-fixes
gnodet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
upgradePropertyInDocument()returnsfalsefor two distinct cases:In case 2, the loop finds nothing in sibling POMs (the property is in the current POM, not there), falls through to this line, and emits
"Property X not found in any project POM properties"— which is factually wrong. The property was found; it just didn't need upgrading.Concrete scenario: Root POM has
<exec.maven.version>3.5.0</exec.maven.version>(already at target). Assembly submodule uses<version>${exec.maven.version}</version>. User runsmvnup.upgradePropertyInDocumenton the current POM returnsfalse(already at min), the pomMap loop finds nothing, warning fires. User sees a confusing "not found" message for a property that is perfectly defined.Fix: track whether the property was found (regardless of upgrade outcome) to suppress the false warning. Add an existence check before the search loop:
Also needs a test: single POM with
<exec.maven.version>3.5.0</exec.maven.version>+ submodule using${exec.maven.version}→ no warning emitted, no modification.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 63c472c. Added an existence check after
upgradePropertyInDocumentreturns false — if the property is present in the current POM's<properties>(or any sibling POM's), we return false immediately without the cross-POM search or the spurious warning. Also added a test for the exact scenario (property already at 3.5.0 + submodule reference → no warning).