You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "gnodet (via GitHub)" <gi...@apache.org> on 2026/08/31 07:35:19 UTC

[PR] [Backport maven-4.0.x] Fix #12931: do not rewrite unmodified POMs in mvnup apply [maven]

gnodet opened a new pull request, #12972:
URL: https://github.com/apache/maven/pull/12972

   Backport of #12938 to `maven-4.0.x`.
   
   ## Summary
   
   `mvnup apply` always logged `Saving modified POMs...` and wrote every discovered POM, even when every strategy reported `0 POM(s) modified`. That both misleads the user and rewrites files that did not change.
   
   `UpgradeResult` already tracks `modifiedPoms`. Apply now:
   
   - writes only those POMs
   - skips the save report entirely when the set is empty
   
   Fixes #12931


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [Backport maven-4.0.x] Fix #12931: do not rewrite unmodified POMs in mvnup apply [maven]

Posted by "gnodet (via GitHub)" <gi...@apache.org>.
gnodet merged PR #12972:
URL: https://github.com/apache/maven/pull/12972


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org