[jbosstools-issues] [JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-20066:
---------------------------------------

[~maxandersen], but that still means that OpenShift tooling was built using parent pom from master - e.g. using Tycho 0.23 instead of 0.22. Isn't that a problem? Another possibility is that it was built using master repos for dependent update site, but my guess is that the jbosstools site stream property was overridden by the jenkins job.

> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
>                 Key: JBIDE-20066
>                 URL: https://issues.jboss.org/browse/JBIDE-20066
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Andre Dietisheim
>            Assignee: Max Rydahl Andersen
>            Priority: Blocker
>             Fix For: 4.3.0.Beta2
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature	3.0.0.Beta2-v20150613-0235-B25	| CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source	3.0.0.Beta2-v20150613-0235-B25	
> org.jboss.tools.openshift.express.feature	3.0.0.Beta2-v20150613-0235-B25	| CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source	3.0.0.Beta2-v20150613-0235-B25	
> org.jboss.tools.openshift.feature	3.0.0.Beta2-v20150613-0235-B25	| CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source	3.0.0.Beta2-v20150613-0235-B25	
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)