[jbosstools-issues] [JBoss JIRA] (JBIDE-10068) Move OpenShift Express client to github

[ https://issues.jboss.org/browse/JBIDE-10068?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-10068: ------------------------------------ Per discussion in IRC today, we have a working build for this, which is coupled to your existing openshift component build: https://hudson.qa.jboss.com/hudson/job/openshift-java-client-master/ https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--op... How will openshift component pick up the new client jar? Is the assumption that it'll see it on the trunk composite site [1] and therefore build against that? If so, then you'll want to add your new component's staging folder [2] and previous staging folder [3] to the composite site in SVN [4], then kick an rsync [5] to push the SVN change to [1]. [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/ [2] http://download.jboss.org/jbosstools/builds/staging/openshift-java-client... [3] http://download.jboss.org/jbosstools/builds/staging.previous/openshift-ja... [4] https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool... [5] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... If not, please clarify. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira