[ https://issues.jboss.org/browse/WFCORE-3718?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-3718: ------------------------------------- I have restored https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess to using sed instructions. However, I think this is not a bug in mvn versions plugin. * wildfly-core-parent has *no* dependency on component-matrix (it is listed in the dependencyManagement with a scope import) * component-matrix is a module of wildfly-core-parent * component-matrix parent is org.jboss:jboss-parent while every other modules in core has org.wildfly.core:wildfly-core-parent has a module * component-matrix defines its groupId and version while every other modules in core inherits this value from org.wildfly.core:wildfly-core-parent According to https://www.mojohaus.org/versions-maven-plugin/set-mojo.html, the version is changed for modules only when they have a parent/child relation to the main module (which is not the case for component-matrix). So I think that the mvn versions plugin is right when it does not update the component-matrix as it is not a child of org.wildfly.core:wildfly-core-parent :) If we wanted to use the mvn version plugins, we would have to use mvn versions:set -DnewVersion=XXX -DprocessAllModules=true -- This message was sent by Atlassian JIRA (v7.5.0#75005)