[
https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19744:
------------------------------------
JBoss parent pom != JBoss Tools parent pom, so you're fine there. And since you're
using our target platform by version (not indirectly via our parent pom) you're
already using the 4.42.0.Final released version rather than the -SNAPSHOT one.
TL;DR, you're fine.
[~maxandersen] [~mickael_istria], please approve this PR:
https://github.com/jbosstools/jbosstools-build/pull/183 so we can delete the .X (upper
case) branch.
jbosstools-build has both 4.2.x and 4.2.X and with different content
--------------------------------------------------------------------
Key: JBIDE-19744
URL:
https://issues.jboss.org/browse/JBIDE-19744
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.2.3.Final
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.2.3.Final
Both
https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and
https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist.
The difference is shown here:
https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x.....
indicating that 4.2.x builds are *not* using the released version of TP to build against
- only snapshot (which should not be there if TP was released)
We should get the 4.2.X deleted, but before we do - what do we do about the missing
commit on 4.2.x ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)