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

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Sep 12 04:02:10 EDT 2013


Max Rydahl Andersen created JBTIS-171:
-----------------------------------------

             Summary: dont 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


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


More information about the jbosstools-issues mailing list