]
RH Bugzilla Integration updated JBDS-2157:
------------------------------------------
Bugzilla Update: Perform
Need to update SOA tooling link (in Central) at GA to point to
external update site
-----------------------------------------------------------------------------------
Key: JBDS-2157
URL:
https://issues.jboss.org/browse/JBDS-2157
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: SOA Tooling / Platform
Affects Versions: 5.0.0.Beta2-SOA
Environment:
http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa...
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa-tooling/devstudio-directory.xml
Reporter: Len DiMaggio
Assignee: Douglas Palmer
Priority: Blocker
Fix For: 5.0.0.Beta3-SOA
Attachments: JBDS-2157.png
Installing SOA tooling from JBoss Central with these jbdevstudio.ini settings:
-vm
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505
-product
com.jboss.jbds.product.product
-showsplash
platform\:/base/plugins/com.jboss.jbds.product
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Xms512m
-Xmx1024m
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa-tooling/devstudio-directory.xml
-Dosgi.instance.area.default=(a)user.home/workspace
Returns a list of older versions of the tooling plugins than is seen here:
http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa...
For example - this version of the BPEL editor is installed from Central:
BPEL Editor (Certified) 1.1.0.v20120501-0347-H6-Beta1-SOA
And this version from
http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa...:
BPEL Editor (Certified) 1.1.0.v20120522-2301-H13-Beta2-SOA
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: