M. Justin created MRELEASE-843: ---------------------------------- Summary: Child modules defined in profiles aren't updated by update-versions Key: MRELEASE-843 URL: https://jira.codehaus.org/browse/MRELEASE-843 Project: Maven 2.x 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"> <modelVersion>4.0.0</modelVersion> <packaging>pom</packaging> <groupId>com.example</groupId> <artifactId>example-parent</artifactId> <version>1.0.0-SNAPSHOT</version> <modules> <module>example-module1</module> </modules> <profiles> <profile> <id>my-profile</id> <modules> <module>example-module2</module> </modules> </profile> </profiles> <scm> <developerConnection>scm: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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira