[MINSTALL-50] provide property filtering on .pom files placed in local repo

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.3
• Component/s: install:install
• Environment: independent
• Flags: Patch
• Assignee: Unassigned
• Reporter: Stefan Armbruster
• Created: 03/Mar/08 07:53
• Updated: 26/Aug/18 19:29
• Resolved: 26/Aug/18 19:29

Description

When maven installs an artifact, it's pom is also copied into the artifact's directory. Unfortunately, if the pom contains a property reference (e.g. ${myprop}), this will not be replaced upon copying the pom file.
I've created a patch for the install plugin that switches on property filtering by setting a mojo parameter "filteringEnabled". Since this defaults to "false", backward compatibility is kept 100%.

Some implementation notes:

• the dirty work is done in FilteredProjectArtifactMetadata.java, the property resolution code has been inspired by ResourcesMojo.
• I've added a unit test, that replaces ${basedir} with the value of a system property.
• since "svn diff" does not handle binary files, src/test/resources/unit/basic-install-test-with-filtering/target/maven-install-test-1.0-SNAPSHOT.jar is not included in the patch. This file is the same as
  src/test/resources/unit/basic-install-test/target/maven-install-test-1.0-SNAPSHOT.jar

Since my knowledge of Maven API is more than limited, there might be a more elegant way to provide this feature ... but it works! I'd be happy to see this in a future release of maven.

Issue Links

• duplicates: MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects
• is depended upon by: MNG-2971 Variables are not replaced into installed pom file
• is related to: MNG-624 automatic parent versioning