[
https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1995:
-------------------------------------
I still don't understand how would adding a property to *.ini file help.
Do you want URLs in the discovery plugin to be dynamic?
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: Snjezana Peco
Fix For: 5.0.0.Beta1
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
-Djbds.soa.site=http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/
and that there's a ${jbds.soa.site} 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