[
https://issues.jboss.org/browse/JBDS-3315?page=com.atlassian.jira.plugin....
]
Mickael Istria closed JBDS-3315.
--------------------------------
Resolution: Done
For sure, I want to take precaution next time. I tried to take some for this time, and
failed at it.
I'm thinking of how to implement a validate-version mojo to spot those issues VERY
early (when building a respin of a component). If we prevent this to happen at root-level,
it shouldn't cascade that far in the process. But this will be a topic for another
Jira.
8.0.2 B378 does not contain updated Forge (possibly more)
---------------------------------------------------------
Key: JBDS-3315
URL:
https://issues.jboss.org/browse/JBDS-3315
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: build
Affects Versions: 8.0.2.GA
Reporter: Martin Malina
Assignee: Mickael Istria
Priority: Blocker
Fix For: 8.0.2.GA
I wanted to check the differences between JBDS 8.0.1 and 8.0.2 and was surprised that
there is no change in Forge plugins - all of the time stamps are from 2014, exactly the
same as was in 8.0.1.
You can see it in the online repo here:
http://www.qa.jboss.com/binaries/RHDS/updates/development/8.0.2.GA-update...
{code}
org.jboss.tools.forge.core_1.3.1.Final-v20141209-0343-B80.jar
org.jboss.tools.forge.m2e_1.1.1.Final-v20141209-0343-B80.jar
org.jboss.tools.forge.runtime.ext_1.3.1.Final-v20141209-0343-B80
org.jboss.tools.forge.runtime_1.4.144.Final-v20141209-0343-B80
org.jboss.tools.forge.ui.notifications_1.3.1.Final-v20141209-0343-B80.jar
org.jboss.tools.forge.ui_1.3.1.Final-v20141209-0343-B80.jar
org.jboss.tools.forge2.runtime_2.12.3.Final-v20141209-0343-B80
{code}
You can see that it's ok in JBoss Tools 4.2.2.Final:
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2....
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)