[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)
jira-events at lists.jboss.org
Thu May 24 12:00:19 EDT 2012
[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBDS-1995:
-----------------------------
Attachment: jbds1995-point-at-Nightly-site-with-new-connector-names.png
jbds1995-point-at-Beta2-site-with-new-connector-names.png
{code}
./jbdevstudio -data /tmp/workspace-foo/ -vmargs -Djboss.discovery.directory.url=http://localhost:8080/product-soa/site/target/site/devstudio-directory.xml -Djboss.soa.update.url=http://localhost:8080/product-soa/site/target/site/
{code}
Result:
!jbds1995-point-at-Nightly-site-with-new-connector-names.png!
{code}
./jbdevstudio -data /tmp/workspace-foo/ -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa-tooling/devstudio-directory.xml -Djboss.soa.update.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa-tooling/
{code}
!jbds1995-point-at-Beta2-site-with-new-connector-names.png!
> 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.Beta3
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Fix For: 5.0.0.CR1
>
> Attachments: jbds-central-override-update-site.png, jbds1995-point-at-Beta2-site-with-new-connector-names.png, jbds1995-point-at-Nightly-site-with-new-connector-names.png, JBDS1995.patch.txt
>
>
> 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.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