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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-1995:
----------------------------------

I fear you're still missing the point. Issue is not the URL of the directory.xml file which then references multiple discovery jars. It's that we need the jar to not change after it's built, but must be able to tell the jar to source the SOA Tooling bits from a place that's different from the URL stated in the discovery.jar's plugin.xml.

>>> It would be nice if we could override that with an internal URL which 
>>> QE could use until such time as the staging site is actually 
>>> populated w/ the latest release/milestone.
> Not sure why we would have to provide a separate setting for SOA. SOA 
> tooling could be treated as any other external plugin (Spring, JRebel, 
> Subclipse...).

Spring, JRebel, Subclipse :: we pull from a single URL which is known well in advance of a release -- either our mirror on dl.jb.org, or the 3rd party site.

SOA Tooling :: we pull from either a public URL (after QE approves) or an internal URL (in order to do QE).

So, where 3rd party stuff is released before we see it, and its URL never changes, SOA Tooling stuff needs to be staged first. Therefore the URL will have to change from what's burned in the plugin to what's used by QE during testing. If it can't be overridden via commandline, then we'll have to edit the plugin AFTER QE approves it to change the URL (or just respin it).

Point is we need a mechanism to support QE and the notion of a changing URL to allow staging before publishing.

Without this, I'd have to publish bits w/o being able to stage them, or would have to respin after QE approval. BOTH scenarios are to be avoided.

                
> 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