Details
-
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
-
Labels:None
-
Environment:Red Hat Linux, Maven 2.0.8, Java 1.6, Cruisecontrol
-
Complexity:Intermediate
-
Number of attachments :
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
-
Activity
Matthias Wegerhoff
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | minimizedPOM.xml [ 38869 ] | |
| Attachment | minimizedSETTINGS.xml [ 38870 ] |
Matthias Wegerhoff
made changes -
| Attachment | minimizedPOM.xml [ 38871 ] |
Brett Porter
made changes -
| Attachment | MNG-3885.zip [ 38872 ] |
Brett Porter
made changes -
Benjamin Bentmann
made changes -
| Summary | Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false | Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile |
Benjamin Bentmann
made changes -
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 2.0.11 [ 14118 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Assignee | Benjamin Bentmann [ bentmann ] | |
| Fix Version/s | 2.1.0-M1 [ 14503 ] |
Benjamin Bentmann
made changes -
| Link |
This issue is duplicated by |
Benjamin Bentmann
made changes -
| Fix Version/s | 3.0-alpha-3 [ 14719 ] |
Benjamin Bentmann
made changes -