[
https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1995 at 2/7/12 11:37 AM:
-----------------------------------------------------------
Handling the location of the discovery.xml is already solved. Either it's hardcoded in
the org.jboss.tools.central plugin, or it's overridden via the jbdevstudio.ini file.
If you don't like the ini file override, then we can hardcode it in the
com.jboss.jbds.central plugin instead. Point is, that's not a concern because in
addition to the hardcoded URL, we have support for the -Dcommandline.override which
empowers QE.
Further discussion of THAT issue should be done in that jira, not here.
was (Author: nickboldt):
Handling the location of the discovery.xml is already solved. Either it's
hardcoded in the org.jboss.tools.central plugin, or it's overridden via the
jbdevstudio.ini file. If you don't like the ini file override, then we can hardcode it
in the com.jboss.jbds.central plugin instead. Point is, that's not a concern because
in addition to the hardcoded URL, we have support for the -Dcommandline.override.
Further discussion of THAT issue should be done in that jira, not here.
externalize URL of JBDS SOA site so it can be passed in via
commandline for testing purposes
--------------------------------------------------------------------------------------------
Key: JBDS-1995
URL:
https://issues.jboss.org/browse/JBDS-1995
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: central
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta1
Attachments: jbds-central-override-update-site.png
We can already do this:
./jbdevstudio -vmargs
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml
But the URL hard-coded in the discovery plugin's plugin.xml [1] will need to change
during QE testing for a milestone release, since the site on which the JBDS SOA bits
reside will be a different URL from where they'll end up when published to Early
Access or once GA'd.
So, we need something like this:
./jbdevstudio -vmargs
-Djboss.soa.update.url=http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/
and that there's a ${jboss.soa.update.url} variable in the plugin.xml of the
discovery plugin [1], which would be set to a default value of
http://devstudio.jboss.com/updates/5.0/soa-tooling/ in plugin.properties [2]
[1]
https://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbd...
[2]
https://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbd...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira