[jbosstools-issues] [JBoss JIRA] (JBIDE-19702) installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin
Nick Boldt (JIRA)
issues at jboss.org
Sun Dec 13 16:11:00 EST 2015
[ https://issues.jboss.org/browse/JBIDE-19702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140585#comment-13140585 ]
Nick Boldt edited comment on JBIDE-19702 at 12/13/15 4:10 PM:
--------------------------------------------------------------
Pushed into 4.3.1.Beta2-SNAPSHOT and 4.4.0.Alpha1-SNAPSHOT and published to nexus:
https://github.com/jbosstools/jbosstools-build-ci/commit/3c6b86cde9e37a7405ea14dd952b7f9cc3478472
https://github.com/jbosstools/jbosstools-build-ci/commit/6c448faf4c6a85b00727f9851e811acf577a426c
With this commit, we actually install EVERYTHING from all the plugin jars found in the directory.xml.
Thus we can install from JBT+JBTCentral+JBTCentralEA, or from JBDS+JBDSCentral+JBDSCentralEA.
HOWEVER, since the Central discovery site includes BOTH the central and earlyaccess plugin jars, we can't yet do an install of just JBT+JBTCentral or JBDS+JBDSCentral as it attempts to then install the EA stuff, but has no URL from which to resolve it.
So either I need to parse the ide-config.properties file to resolve missing URLs to add to EXTRA_SITES, or we need to ensure that the discovery site only contains plugins whose content can be found from that same site's composite.
Thus, this will work:
{code}installFromCentral.sh -INSTALL_PLAN "https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_4.3.mars/latest/all/repo/;https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.earlyaccess_4.3.mars/latest/all/repo/devstudio-directory.xml"{code}
but this will fail:
{code}installFromCentral.sh -INSTALL_PLAN "https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_4.3.mars/latest/all/repo/;https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_4.3.mars/latest/all/repo/devstudio-directory.xml"{code}
was (Author: nickboldt):
Pushed into 4.3.1.Beta2-SNAPSHOT and 4.4.0.Alpha1-SNAPSHOT and published to nexus:
https://github.com/jbosstools/jbosstools-build-ci/commit/3c6b86cde9e37a7405ea14dd952b7f9cc3478472
https://github.com/jbosstools/jbosstools-build-ci/commit/6c448faf4c6a85b00727f9851e811acf577a426c
> installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19702
> URL: https://issues.jboss.org/browse/JBIDE-19702
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> Today, installFromCentral.sh assumes two incorrect things:
> a) central URL is always different than the JBT/JBDS site URL [no longer true, since JBT/JBDS & Central content are now co-located]
> b) the plugin to parse for IUs is ONLY the central one, not the EA one [we should parse ONE or BOTH, depending on cmdline flag]
> {code}
> # get a list of IUs to install from the Central site (based on the discovery.xml -> plugin.jar -> plugin.xml)
> CENTRAL_URL=${INSTALL_PLAN#*,} # includes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
> if [[ $CENTRAL_URL != $INSTALL_PLAN ]]; then
> # echo $CENTRAL_URL
> wget ${CENTRAL_URL} -q --no-check-certificate -N -O directory.xml
> PLUGINJAR=`cat ${WORKSPACE}/directory.xml | egrep "org.jboss.tools.central.discovery_|com.jboss.jbds.central.discovery_" | sed "s#.\+url=\"\(.\+\).jar\".\+#\1.jar#"`
> # echo "Got $PLUGINJAR"
> CENTRAL_URL=${SITES#*,} # excludes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL
> wget ${CENTRAL_URL}/${PLUGINJAR} -q --no-check-certificate -N -O plugin.jar
> unzip -oq plugin.jar plugin.xml
> ...
> {code}
> https://github.com/jbosstools/jbosstools-build-ci/blob/4.3.x/util/installFromCentral.sh
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list