[
https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi...
]
Mat Booth commented on JBIDE-23677:
-----------------------------------
Probably related, this seems to cause some "push to staging" sanity check to
fail, for example:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
{code}
04:22:18 + echo 'In foundation.core, want 4.4.4.AM1, got 4.4.3.AM1 from
org.jboss.tools.foundation.core_1.3.4.AM1-v20170309-1126-B65.jar'
04:22:18 + egrep 'foundation.core|4.4.4.AM1'
04:22:18 In foundation.core, want 4.4.4.AM1, got 4.4.3.AM1 from
org.jboss.tools.foundation.core_1.3.4.AM1-v20170309-1126-B65.jar
04:22:18 + [[ 4.4.4.AM1 != 4.4.3.AM1 ]]
{code}
write maven enforcer test to ensure we set correct version of
foundation.core (based on parent pom version)
------------------------------------------------------------------------------------------------------------
Key: JBIDE-23677
URL:
https://issues.jboss.org/browse/JBIDE-23677
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, foundation
Affects Versions: 4.4.3.AM1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.4.AM1, 4.5.0.AM1
Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2.
https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)