[MNG-3885] Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.8
• Fix Version/s: 2.0.11, 2.1.0-M1, 3.0-alpha-3
• Component/s: Deployment
• Environment: Red Hat Linux, Maven 2.0.8, Java 1.6, Cruisecontrol
• Assignee: Benjamin Bentmann
• Reporter: Matthias Wegerhoff
• Created: 02/Dec/08 09:17
• Updated: 05/Apr/15 23:00
• Resolved: 24/Jan/09 11:49

Description

When deploying artifacts into local repository with cruisecontrol by using the following command:

mvn -U -P mvn-profile ... -DuniqueVersion=false deploy

The parent is always beeing deployed correctly, without timestamp as <MODULE_VERSION>-SNAPSHOT. But all Modules are beeing deployed with Timestamp.

Issue Links

• depends upon: MNG-4009 [regression] Effects of active profiles from parent are not inherited by children.
• is duplicated by: MDEPLOY-57 <uniqueVersion>false</uniqueVersion> not honored inside <profile>
• supercedes: MNG-2470 uniqueVersion not inherited in child projects