efegokdemir opened a new pull request, #1510:
URL: https://github.com/apache/maven-release/pull/1510

   ## Summary
   
   `release:prepare` can inline a resolved snapshot version into a dependency 
when the dependency version is defined through a local property. The property 
remains a snapshot, so the rewritten POM loses the shared property reference 
and can retain stale release data.
   
   This changes the POM rewrite path to reuse the existing local-property 
update logic for resolved snapshot dependencies, while retaining 
literal-version fallback for inherited, read-only, or otherwise unresolvable 
properties.
   
   Fixes #1470
   
   ## Changes
   
   - Preserve local dependency version expressions while updating their 
property value.
   - Keep the existing fallback for properties that cannot be rewritten locally.
   - Add a release-POM regression fixture covering the resolved snapshot case.
   
   ## Testing
   
   - `mvn -pl maven-release-manager -am -Dspotless.check.skip=true 
-Dspotless.apply.skip=true -Dcheckstyle.skip=true -Drat.skip=true test` — 
passed (770 tests, 18 skipped).
   - Focused regression failed on the unchanged implementation and passed with 
this change.
   - `mvn -pl maven-release-manager -am -DskipTests -Dspotless.check.skip=true 
-Dspotless.apply.skip=true -Dcheckstyle.skip=true apache-rat:check` — passed.
   - `git diff --check` — passed.
   - Spotless check was attempted but is blocked by the local Java/Palantir 
formatter incompatibility (`NoSuchFieldError` in `com.sun.tools.javac.tree`).
   
   ## Notes
   
   This contribution was developed with AI assistance. I reviewed the complete 
diff, reproduced the regression, and ran the listed checks. No competing open 
PR for #1470 was found; PR #1500 addresses a separate previous-version property 
case.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to