Problem
#4426 introduced Maven CI-friendly ${revision} versioning with flatten-maven-plugin, but also committed 10 .flattened-pom.xml files into the repository.
These files are build artifacts generated during process-resources (like target/). They should not be version-controlled.
Apache SeaTunnel uses the same ${revision} + flatten-maven-plugin approach and explicitly gitignores them:
Expected behavior
- Source
pom.xml files keep ${revision} for centralized version management
flatten-maven-plugin remains configured for install/deploy
.flattened-pom.xml is generated locally during Maven builds but never committed
Proposed fix
- Add
*.flattened-pom.xml to .gitignore
- Remove the 10 committed
.flattened-pom.xml files from the repo
Related: #4426
Problem
#4426 introduced Maven CI-friendly
${revision}versioning withflatten-maven-plugin, but also committed 10.flattened-pom.xmlfiles into the repository.These files are build artifacts generated during
process-resources(liketarget/). They should not be version-controlled.Apache SeaTunnel uses the same
${revision}+flatten-maven-pluginapproach and explicitly gitignores them:Expected behavior
pom.xmlfiles keep${revision}for centralized version managementflatten-maven-pluginremains configured for install/deploy.flattened-pom.xmlis generated locally during Maven builds but never committedProposed fix
*.flattened-pom.xmlto.gitignore.flattened-pom.xmlfiles from the repoRelated: #4426