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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] 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. 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. -- 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