[jbosstools-issues] [JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-23036:
------------------------------------

No, because JBT 4.4.0 users are using the 4.60.0.Final TP, not the forthcoming 4.60.1.Final one. Won't even affect 4.4.1.AM1 / AM2 / AM3 users because they can still update to the latest as it'll be included in JBT/devstudio update site directly, instead of the JBT/devstudio TP. 

All we're doing it moving it from one site to the other, but the composite site users see will still have all the same docker tooling features. (Well, it'll have NEWER versions.)

> Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23036
>                 URL: https://issues.jboss.org/browse/JBIDE-23036
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, docker, openshift, target-platform
>    Affects Versions: 4.4.1.AM3
>            Reporter: Nick Boldt
>
> In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular:
> * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror)
> * remove docker/vagrant tooling from target platform
> * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)