[jbosstools-issues] [JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml

[Nick Boldt (JIRA)]

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

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.

                  
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
>                 Key: JBTIS-171
>                 URL: https://issues.jboss.org/browse/JBTIS-171
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: distribution
>            Reporter: Max Rydahl Andersen
>            Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
>  siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>       
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
>  siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"

--
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