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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1995: ---------------------------------- Sure, that can work, BUT that means: a) passing in a different URL for the directory.xml [0], which points at b) some different discovery.jar [1], in which a different c) soa tooling update site [2] is hardcoded Thus when we start the stable_branch cycle, we'd need to change the JBDS SOA Central Discovery plugin.xml to point at the new URL during testing cycle [2], then when it passes QE, *we'd have to change it again, rebuild it, and re-release it* to point at the published URL [3]. [0] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... [1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... [2] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... [3] http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/ -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1995: ---------------------------------- Wouldn't we just do: {code} jbds.soa.site=http://devstudio.jboss.com/updates/5.0/ {code} like any other property in 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1995: ------------------------------------- We can programmatically define some stable URLs for different versions of JBDS/JBT using IJBossCentraConfigurator (the org.jboss.tools.central.configurators ext.point ). When testing, the jboss.discovery.directory.url system property can be set in a testing discovery.xml file. The discovery.xml file can contain more plugins: the standard JBDS/JBT discovery plugin, SOA plugin ... -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-1995: ------------------------------------- I still don't understand how would adding a property to *.ini file help. Do you want URLs in the discovery plugin to be dynamic? -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-1995: -------------------------------- Assignee: Nick Boldt (was: Snjezana Peco) -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1995 at 2/7/12 1:59 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.... {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. 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. -- 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

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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1995 at 2/7/12 2:56 AM: ---------------------------------------------------------- Trying to override hardcoded value in plugin.properties, which points at M5 site: {code} ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://localhost:8080/product-soa/site/target/site/devstudio-directory.xml -Djboss.soa.update.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.soa-tooling.updatesite/product-soa/ {code} But instead of seeing the Beta1 bits from trunk nightly, we still see M5: !jbds-central-override-update-site.png! was (Author: nickboldt): Trying to override hardcoded value in plugin.properties, which points at M5 site: {code} ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://localhost:8080/product-soa/site/target/site/devstudio-directory.xml -Djboss.soa.update.url=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.soa-tooling.updatesite/product-soa/ {code} But instead of seeing the Beta1 bits from trunk nightly, we still see M5: !jbds-central-override-update-site.png! -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1995 at 2/7/12 3:01 AM: ---------------------------------------------------------- Wouldn't we just do: {code} jboss.soa.update.url=http://devstudio.jboss.com/updates/5.0/ {code} like any other property in plugin.properties? Note too it occurs to me we need to do this for both JBT and JBDS. :( was (Author: nickboldt): Wouldn't we just do: {code} jbds.soa.site=http://devstudio.jboss.com/updates/5.0/ {code} like any other property in plugin.properties? Note too it occurs to me we need to do this for both JBT and JBDS. :( -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1995: ----------------------------- Description: 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.jbd... [2] https://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbd... was: 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1995: ------------------------------------------- note, lets get the core problem fixed first (handling of the initial discovery.xml ;) before doing this one. Fixing (if at all) this I believe is best done with either A) adding support for multiple discovery sites contributed via extension points B) by adding support for allowing ${some.property:defaultvalue} in the updatesite url. A introduces the problem of overlapping discovery sites and possible conflicts between which plugin contributes what. B is probably the simplest approach but not sure if we control the reading of those plugin xml values - do we Snjezana? -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1995 at 2/7/12 11:37 AM: ----------------------------------------------------------- Handling the location of the discovery.xml is already solved. Either it's hardcoded in the org.jboss.tools.central plugin, or it's overridden via the jbdevstudio.ini file. If you don't like the ini file override, then we can hardcode it in the com.jboss.jbds.central plugin instead. Point is, that's not a concern because in addition to the hardcoded URL, we have support for the -Dcommandline.override which empowers QE. Further discussion of THAT issue should be done in that jira, not here. was (Author: nickboldt): Handling the location of the discovery.xml is already solved. Either it's hardcoded in the org.jboss.tools.central plugin, or it's overridden via the jbdevstudio.ini file. If you don't like the ini file override, then we can hardcode it in the com.jboss.jbds.central plugin instead. Point is, that's not a concern because in addition to the hardcoded URL, we have support for the -Dcommandline.override. Further discussion of THAT issue should be done in that jira, not here. -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1995: ----------------------------- Fix Version/s: 5.0.0.Beta3-SOA (was: 5.0.0.CR1) Affects Version/s: 5.0.0.Beta2-SOA (was: 5.0.0.M5) -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-1995: ----------------------------- Attachment: JBDS1995.patch.txt Patch to add support for -Djboss.soa.update.url: [^JBDS1995.patch.txt]. Still testing locally to ensure this actually works... -- 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

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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-1995 at 5/24/12 12:23 PM: ------------------------------------------------------------ Patch appears to work. Had to rebuild JBDS .all feature like this: cd ~/JBT/trunk/examples; mvn clean install -f ../build/pom.xml -Pdefault,local.site,examples-bootstrap -DskipTests cd ~/JBDS/trunk/product; mvn clean install -f pom-site-and-product.xml Then update JBDS from ~/JBDS/trunk/product/features/com.jboss.jbds/target/repository/ folder (to get newer examples feature built above), restart, and launch it like this: {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} In central, we see: !jbds1995-point-at-Nightly-site-with-new-connector-names.png! And after installing, I get these features: {code} drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 com.jboss.jbds.bpel.feature_1.1.0.v20120524-1530-H28-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.bpel.feature_1.1.0.v20120521-1335-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.esb.feature_1.5.0.v20120521-1320-H14-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm.common.feature_4.4.0.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm.convert.feature_1.0.0.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm3.feature_3.2.1.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.modeshape.rest.feature_1.1.0.v20120521-1348-H6-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.drools.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.esb.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.jbpm.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jbpm.gd.jpdl.feature_3.2.1.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.datatools.connectivity.feature_7.7.1.v20120521-1448-H41-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.designer.feature_7.7.1.v20120521-1448-H41-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.designer.runtime.feature_7.7.1.v20120521-1448-H41-Nightly-SOA {code} ---- Alternatively, launching like this: {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} I see this in Central: !jbds1995-point-at-Beta2-site-with-new-connector-names.png! And after installing, I get these features: {code} drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 com.jboss.jbds.bpel.feature_1.1.0.v20120522-2301-H13-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.bpel.feature_1.1.0.v20120521-1328-H2-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.esb.feature_1.5.0.v20120522-1349-H12-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm.common.feature_4.4.0.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm.convert.feature_1.0.0.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm3.feature_3.2.1.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.modeshape.rest.feature_1.1.0.v20120521-1354-H2-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.drools.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.esb.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.jbpm.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jbpm.gd.jpdl.feature_3.2.1.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.datatools.connectivity.feature_7.7.1.v20120521-1528-H9-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.designer.feature_7.7.1.v20120521-1528-H9-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.designer.runtime.feature_7.7.1.v20120521-1528-H9-Beta2-SOA {code} So... just need a +1 from Max and I can commit this to trunk. was (Author: nickboldt): {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! Installed: {code} drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 com.jboss.jbds.bpel.feature_1.1.0.v20120524-1530-H28-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.bpel.feature_1.1.0.v20120521-1335-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.esb.feature_1.5.0.v20120521-1320-H14-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm.common.feature_4.4.0.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm.convert.feature_1.0.0.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.jbpm3.feature_3.2.1.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.modeshape.rest.feature_1.1.0.v20120521-1348-H6-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.drools.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.esb.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jboss.tools.runtime.jbpm.detector.feature_1.3.0.v20120521-1716-H11-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:03 org.jbpm.gd.jpdl.feature_3.2.1.v20120521-1346-H8-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.datatools.connectivity.feature_7.7.1.v20120521-1448-H41-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.designer.feature_7.7.1.v20120521-1448-H41-Nightly-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:04 org.teiid.designer.runtime.feature_7.7.1.v20120521-1448-H41-Nightly-SOA {code} ---- Alternatively: {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} Result: !jbds1995-point-at-Beta2-site-with-new-connector-names.png! Installed: {code} drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 com.jboss.jbds.bpel.feature_1.1.0.v20120522-2301-H13-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.bpel.feature_1.1.0.v20120521-1328-H2-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.esb.feature_1.5.0.v20120522-1349-H12-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm.common.feature_4.4.0.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm.convert.feature_1.0.0.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.jbpm3.feature_3.2.1.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.modeshape.rest.feature_1.1.0.v20120521-1354-H2-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.drools.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.esb.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jboss.tools.runtime.jbpm.detector.feature_1.3.0.v20120522-1702-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.jbpm.gd.jpdl.feature_3.2.1.v20120521-1345-H4-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.datatools.connectivity.feature_7.7.1.v20120521-1528-H9-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.designer.feature_7.7.1.v20120521-1528-H9-Beta2-SOA drwxrwxr-x 3 nboldt nboldt 4.0K May 24 12:00 org.teiid.designer.runtime.feature_7.7.1.v20120521-1528-H9-Beta2-SOA {code} -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1995: ------------------------------------------- noway this patch goes into jboss tools source code. Central code should know *nothing* about "SOA" or any other specific site beyond its main site. Any "magic" property replacement is to happen somewhere else - not here. I also do not grok what the patch is actually trying to do - it seems to just add a method with a url and nothing else. -- 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

[ https://issues.jboss.org/browse/JBDS-1995?page=com.atlassian.jira.plugin.... ] Douglas Palmer resolved JBDS-1995. ---------------------------------- Fix Version/s: 5.0.0.CR1-SOA (was: 5.0.0.Beta3-SOA) Resolution: Done While it wasn't technically possible to externalise this property we have added a maven resource filter so that this property can be set at build time. -- 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