[
https://issues.jboss.org/browse/JBDS-1996?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1996:
----------------------------------
1. Added the above entry to the 4 jbdevstudio.ini files I found in the JBDS svn repo.
2. Created a new devstudio-directory.xml file, and placed it here:
http://devstudio.jboss.com/updates/5.0/devstudio-directory.xml
3. Pointed said directory file at two cached versions of the discovery plugins -- one for
JBT, one for JBDS.
4. Kicked a build to verify:
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.product/914/
5. When build is done, upon startup we should see a mix of JBT and JBDS contributions in
Central's Update listing. Specifically, we should see GWT and JRebel (only on JBT
site) and SOA Tooling (only on JBDS site).
If this works, we can then put the SOA Tooling stuff into its own plugin, so that it's
100% independent of the Core release schedule. When SOA releases, they would need only to
update
http://devstudio.jboss.com/updates/5.0/devstudio-directory.xml to point at their
newer plugin.
tweak jbdevstudio.ini to load the correct JBDS Central URL
----------------------------------------------------------
Key: JBDS-1996
URL:
https://issues.jboss.org/browse/JBDS-1996
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Build, central, installer
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Fix For: 5.0.0.Beta1
In order that JBDS use a different discovery plugin than JBoss Tools, we need to tweak
jbdevstudio.ini to load the correct URL for the site:
... -vmargs
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml
--
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