[MNG-4319] Property expansion does not work for goals in plugin executions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0-M1, 2.1.0, 2.2.0, 2.2.1
• Fix Version/s: 2.2.2, 3.0-alpha-2
• Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200); Java version: 1.6.0_02; Default locale: de_DE, platform encoding: Cp1252; OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
• Assignee: Benjamin Bentmann
• Reporter: Marc Rohlfs
• Created: 25/Aug/09 03:58
• Updated: 13/Sep/10 12:10
• Resolved: 31/Oct/09 09:18

Description

I am using a (global) property to control the goal(s) of the Assembly Plugin to be executed:

<goals>
  <goal>${build.assembly.goal}</goal>
</goals>

The property is pre-defined in my (parent) POM and may be overwritten using the -D option on the command line or (for convenience) using a profile. This is (was) a very convenient way to switch from ZIP (goal single) to directory (goal directory-single) packaging during development of programm packages.

When I tried to upgrade from Maven 2.0.10 to Maven 2.2.1 I noticed that this doesn't work any more. I also tried intermediate versions and it seems that 2.0.10 was the last version where it works.

Issue Links

• is duplicated by: MNG-4808 Maven does not resolve variables within a plugin's <goal>
• is related to: MNG-3679 <execution><id>${some.custom.var}</id> ... broke
• relates to: MNG-4422 [regression] Property expansion does not work for phase of plugin executions