[
https://issues.jboss.org/browse/WFCORE-3718?page=com.atlassian.jira.plugi...
]
Tomaz Cerar commented on WFCORE-3718:
-------------------------------------
Yes, idea is that component-matrix has no dependencies to anything, jboss-parent is there
just to make sure the release process (plugin settings) is the same across the project.
Maybe solution for this would be to add configuration of versions plugin to
pluginManagment to always have processAllModules configured, this way person doing release
wouldn't need to be extra careful.
mvn versions:set -DnewVersion=xxxx does not replace
component-matrix/pom.xml
----------------------------------------------------------------------------
Key: WFCORE-3718
URL:
https://issues.jboss.org/browse/WFCORE-3718
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 5.0.0.Alpha2
Reporter: Kabir Khan
Assignee: Tomaz Cerar
{quote}
[2:26 PM] Kabir Khan: @ctomc following
https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using
mvn versions:set -DnewVersion=5.0.0.Alpha2
[2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT
[2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT"
component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version>
[2:27 PM] Tomaz Cerar: damn, that is not good
[2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases
[2:27 PM] Kabir Khan: Should it be in the list of modules?
[2:27 PM] Tomaz Cerar: it is
{quote}
All other versions are correctly replaced. I'd hazard a guess that this also happens
in WF full.
CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)