[jbosstools-issues] [JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614101#comment-13614101 ] 

Nick Boldt commented on JBIDE-26283:
------------------------------------

Looking at the spec for compare-version-with-baselines [1], one of the illegal versions is "same fully-qualified version as baseline, but with different binary content", which is what we're seeing here. 

[1] https://www.eclipse.org/tycho/sitedocs-extras/tycho-p2-extras-plugin/compare-version-with-baselines-mojo.html

So... as I'm not sure why this is happening other than the usual "someone forgot to bump a version after we released 4.6.0.Final", I'm bumping versions.

Base: https://github.com/jbosstools/jbosstools-base/commit/0594f0a41a1ceec00e72b0ab2960dae6b1de5d55
Central: https://github.com/jbosstools/jbosstools-central/commit/df3719f1ce67e6106450944803644be5f1bca53f

Appears to be the same problem in forge, javaee, jst, openshift, vpe, webservices. 

> Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-26283
>                 URL: https://issues.jboss.org/browse/JBIDE-26283
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.9.0.AM1
>            Reporter: Josef Kopriva
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.9.0.AM2
>
>
> Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-base_master/ is red for one week.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)