[
https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-23768:
---------------------------------------
The downside of this is that tags of github repos were created before this was done and
now they contain a reference to the snapshot version of parent pom and the build is broken
in the tag.
For example see here:
https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.4.3.Fin...
I suggested a fix here:
https://github.com/jbosstools/jbosstools-server/pull/469
Next time the parent pom should be released first, then the change pushed to the depending
repos and finally make the release tag.
Even here, we could fix this in all repos in jbosstools-4.4.3.x branch and then update the
jbosstools-4.4.3.Final tag.
Publish tagged version of jboss tools parent pom to public
repository
---------------------------------------------------------------------
Key: JBIDE-23768
URL:
https://issues.jboss.org/browse/JBIDE-23768
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.4.2.Final, 4.4.3.AM1
Reporter: Aurélien Pupier
Assignee: Nick Boldt
Labels: releasework
Fix For: 4.4.3.Final
it will allow Fuse Tooling (and other dependent projects) to have tagged version of their
parent pom for tagged release.
i'm talking about org.jboss.tools:parent
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)