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

Tue Feb 7 02:00:49 EST 2012

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

Nick Boldt edited comment on JBDS-1995 at 2/7/12 2:00 AM:
----------------------------------------------------------

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)
* plugin.xml / plugin.properties (with reference to SOA Tooling site

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.soa-tooling.updatesite/product-soa/
{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.-

Updated the TP and spun locally like this:

{code}
 mvn3 clean install -f pom-discovery-feature-site.xml -Plocal.site -Dlocal.site=file:///home/nboldt/tru/build/target-platform/JBDS_REPO/

[INFO] com.jboss.jbds.central.discovery.soa-tooling ...... SUCCESS [0.997s]
[INFO] com.jboss.jbds.central.discovery.soa-tooling.feature  SUCCESS [0.098s]
[INFO] JBDS - Central Discovery Plugin + Feature and Site - SOA Tooling  SUCCESS [0.005s]
[INFO] com.jboss.jbds.site.product.soa-tooling ........... SUCCESS [10.517s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}

Then, I updated by hand a directory.xml file to point at both the Core and SOA discovery plugins:

{code}
<directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/">
<entry url="http://localhost:8080/product/site/target/site/plugins/com.jboss.jbds.central.discovery_1.0.0.v20120207-0622-Beta1.jar" permitCategories="true"/>
<entry url="http://localhost:8080/product-soa/site/target/site/plugins/com.jboss.jbds.central.discovery.soa-tooling_1.0.0.v20120207-0630-Beta1.jar" permitCategories="true"/>
</directory>
{code}

And while the externalized property IS read correctly, and I see Beta1 SOA Tooling bits I can install, I can't override it like this to allow testing the installation of M5 bits:

{code}
./jbdevstudio -vmargs 
-Djboss.discovery.directory.url=http://localhost:8080/product/site/target/site/devstudio-directory.xml 
-Djbds.soa.site=http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/
{code}

----

So, I need some way to have the *com.jboss.jbds.central.discovery.soa-tooling* plugin look at the system property *jbds.soa.site* in the same way that the *org.jboss.tools.central* plugin looks at *jboss.discovery.directory.url*.

      was (Author: nickboldt):
    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.