Skip to content

Strip super POM properties from generated release POMs - #1520

Closed
slachiewicz wants to merge 1 commit into
masterfrom
agent/strip-super-pom-properties
Closed

slachiewicz wants to merge 1 commit into
masterfrom
agent/strip-super-pom-properties

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Maven 3.10 and Maven 4 declare encoding and outputTimestamp defaults in the super POM (apache/maven#12032, MNG-8258), so release:prepare-with-pom wrote them into every release-pom.xml, including a fixed 1980 project.build.outputTimestamp. Properties equal to the super POM default are now dropped unless the project or a parent declares them.

Maven 3.10 and Maven 4 add encoding and project.build.outputTimestamp defaults to the super POM (apache/maven#12032, MNG-8258), and createReleaseModel writes release-pom.xml from the effective model, so every release POM inherited them, including a fixed 1980 outputTimestamp. Drop properties equal to the super POM default unless the project or a parent declares them.
@slachiewicz slachiewicz added bug Something isn't working wontfix This will not be worked on labels Oct 5, 2026
@slachiewicz slachiewicz closed this Oct 7, 2026
@slachiewicz
slachiewicz deleted the agent/strip-super-pom-properties branch October 7, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working wontfix This will not be worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant