[jbosstools-issues] [JBoss JIRA] (JBDS-1995) externalize URL of JBDS SOA site so it can be passed in via commandline for testing purposes

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Mon Feb 6 15:13:48 EST 2012


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

Snjezana Peco commented on JBDS-1995:
-------------------------------------

We can programmatically define some stable URLs for different versions of JBDS/JBT using IJBossCentraConfigurator (the org.jboss.tools.central.configurators ext.point ).
When testing, the jboss.discovery.directory.url system property can be set in a testing discovery.xml file.
The discovery.xml file can contain more plugins: the standard JBDS/JBT discovery plugin, SOA plugin ...
                
> 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.jbds.central.discovery/plugin.xml
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds.central.discovery/plugin.properties

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

        


More information about the jbosstools-issues mailing list