[
https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-19744.
------------------------------
Resolution: Done
* Target platform is already so tagged:
https://github.com/jbosstools/jbosstools-target-platforms/tree/4.42.0.Final
* PR pushed to jbosstools-build 4.2.x branch (lowercase), AFTER the jbosstools-4.2.3.Final
tag.
* Branch jbosstools-4.2.X (uppercase) deleted:
{code}
$➔ git push origin :jbosstools-4.2.X
To git@github.com:jbosstools/jbosstools-build.git
- [deleted] jbosstools-4.2.X
{code}
Closing.
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)