[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:
----------------------------------
ini file is a different issue. THIS issue is regarding parameterizing the URL from which
SOA Tooling bits are installed, as referenced by the Central Discovery plugin.
So, once again, the 3 moving pieces are:
* directory.xml (contains references to 1 or more discovery jars - 1 for Core and later, 1
for SOA Tooling)
* discovery.jar(s) (containing plugin.xml and plugin.properties)
I'm working on a new com.jboss.jbds.central.discovery.soa-tooling.feature and
com.jboss.jbds.central.discovery.soa-tooling plugin which will set this in the
plugin's plugin.properties:
{code}
jbds.soa.site =
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk....
{code}
Then, in plugin.xml, we should be able to do something like this:
{code}
<connectorDescriptor id="com.jboss.jbds.bpel.feature"
categoryId="com.jboss.jbds.central.discovery.soa-tooling"
groupId="com.jboss.jbds.central.discovery.soa-tooling.bcdg"
kind="task" license="Free, EPL" provider="JBoss by
Red Hat"
siteUrl="%jbds.soa.site"
name="JBoss BPEL Editor" description="BPEL Editor, examples and
cheatsheets">
<iu id="com.jboss.jbds.bpel.feature"/>
<iu id="org.jboss.tools.bpel.feature"/>
<iu id="org.eclipse.bpel.apache.ode.runtime.feature"/>
<icon image32="images/jbds_bpel_32.png"></icon>
<overview url="http://devstudio.jboss.com/"></overview>
</connectorDescriptor>
{code}
So, yes, I want a way to pass in a different value for %jbds.soa.site. I'm hoping that
by externalizing the property, I can now do -Djbds.soa.site=http://some.other.url.
Unfortunately, I'm blocked right now because the TP is missing a feature, which
prevents the BPEL component from building, which then blocks the SOA Tooling site from
building. Will update when I have that sorted out.
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