[
https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin....
]
Paul Leacu commented on JBTIS-171:
----------------------------------
So - the current discovery solution establishes a new generated/merged JBDSIS
directory.xml file containing both JBDSIS and JBDS Core content in a single file. The
Jenkins job needed to generate that xml file is JBDSIS-aggregate-disc. No content is lost
as long as the previous entry URLs are preserved in the merged/new directory xml file.
If this is cool with everyone, I'll close this Jira tomorrow...
If not - you know what to do... :)
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/upd...
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://devst...
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...
in stack:
siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integrat...
--
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