[jira] [Commented] (MRELEASE-843) Child modules defined in profiles aren't updated by update-versions

2015-04-07 Thread M. Justin (JIRA) 

[ 
https://issues.apache.org/jira/browse/MRELEASE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483925#comment-14483925
 ] 

M. Justin commented on MRELEASE-843:


Inactive, per my included example.

 Child modules defined in profiles aren't updated by update-versions
 ---

 Key: MRELEASE-843
 URL: https://issues.apache.org/jira/browse/MRELEASE-843
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: update-versions
Reporter: M. Justin

 When I do a mvn:update-versions for a multi-module project that has one of 
 its modules defined in a profile, the modules defined in the profile don't 
 have their versions updated.  I would expect these modules to also be updated.
 {code:title=pom.xml}project xmlns=http://maven.apache.org/POM/4.0.0; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/maven-v4_0_0.xsd;
   modelVersion4.0.0/modelVersion
   packagingpom/packaging
   groupIdcom.example/groupId
   artifactIdexample-parent/artifactId
   version1.0.0-SNAPSHOT/version
   modules
 moduleexample-module1/module
   /modules
   
   profiles
 profile
   idmy-profile/id
   modules
 moduleexample-module2/module
   /modules
 /profile
   /profiles
   scm
  
 developerConnectionscm:git:examplerepo:example.git/developerConnection
/scm
 /project
 {code}
 In this example, when I execute mvn release:update-versions, I get queried to 
 update example-parent and example-module1, but not example-module2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MRELEASE-843) Child modules defined in profiles aren't updated by update-versions

2015-04-06 Thread Robert Scholte (JIRA) 

[ 
https://issues.apache.org/jira/browse/MRELEASE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481084#comment-14481084
 ] 

Robert Scholte commented on MRELEASE-843:
-

Are we talking about active or inactive profiles?

 Child modules defined in profiles aren't updated by update-versions
 ---

 Key: MRELEASE-843
 URL: https://issues.apache.org/jira/browse/MRELEASE-843
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: update-versions
Reporter: M. Justin

 When I do a mvn:update-versions for a multi-module project that has one of 
 its modules defined in a profile, the modules defined in the profile don't 
 have their versions updated.  I would expect these modules to also be updated.
 {code:title=pom.xml}project xmlns=http://maven.apache.org/POM/4.0.0; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/maven-v4_0_0.xsd;
   modelVersion4.0.0/modelVersion
   packagingpom/packaging
   groupIdcom.example/groupId
   artifactIdexample-parent/artifactId
   version1.0.0-SNAPSHOT/version
   modules
 moduleexample-module1/module
   /modules
   
   profiles
 profile
   idmy-profile/id
   modules
 moduleexample-module2/module
   /modules
 /profile
   /profiles
   scm
  
 developerConnectionscm:git:examplerepo:example.git/developerConnection
/scm
 /project
 {code}
 In this example, when I execute mvn release:update-versions, I get queried to 
 update example-parent and example-module1, but not example-module2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)