[MNG-4140] Properties incorrectly replaced in pom

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.2.0
• Assignee: John Dennis Casey
• Reporter: Reinhard Nägele
• Created: 20/Apr/09 01:26
• Updated: 07/Jul/09 12:29
• Resolved: 21/Apr/09 17:56

Description

The attached sample pom configures the dependency plugin. During an install, ${project.version} is replaced by the actual version when in fact no replacement at all must happen (see pom-transformed.xml). This seems to be related to the version, since all other properties remain unchanged.

In our real world scenario, the dependency plugin is configured in a profile in order to copy child module artifacts to Luntbuild's publish directory. This, of course, won't work if the version is replaced during install. It must be evaluated at runtime.

This is a regression in Maven 2.1.0. Maven 2.0.10 does not have the problem.

Issue Links

• is related to: MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects