[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-171 at 9/13/13 7:54 PM: ----------------------------------------------------------- I was able to reproduce your problem using the Beta1 site. But I have a simpler solution, which uses the existing build.xml script to generate the staging discovery site that QE can use to perform an installation. I've fixed the two JBTIS and JBDSIS jobs [1], [2] so that they now pass in a value of UPSTREAM_EXTRAS_SITE to the composite site, which will therefore allow installation of JBDS Central and JBDS IS Central content from a single overriding URL. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-disc/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBDSIS-aggregate-disc/ To verify this is fixed, try one of these URLs when configuring jbdevstudio.ini: {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/ {code} or {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2/ {code} The benefit here is that the job can now be configured when run to produce a composite site which is a mix of any specific upstream versions of JBDS+Central+TP or JBT+Central+TP (or simply use the latest changing released version). So we can produce a staging discovery site that would target JBDS 7.0 or 7.1, simply by re-running the job. was (Author: nickboldt): I was able to reproduce your problem using the Beta1 site. But I have a simpler solution, which uses the existing build.xml script to generate the staging discovery site that QE can use to perform an installation. I've fixed the two JBTIS and JBDSIS jobs [1], [2] so that they now pass in a value of UPSTREAM_EXTRAS_SITE to the composite site, which will therefore allow installation of JBDS Central and JBDS IS Central content from a single overriding URL. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-disc/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBDSIS-aggregate-disc/ To verify this is fixed, try one of these URLs when configuring jbdevstudio.ini: {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1a/ {code} or {code} -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2a/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2a/ {code} The benefit here is that the job can now be configured when run to produce a composite site which is a mix of any specific upstream versions of JBDS+Central+TP or JBT+Central+TP (or simply use the latest changing released version). So we can produce a staging discovery site that would target JBDS 7.0 or 7.1, simply by re-running the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira