[
https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9029:
-----------------------------------
Latest nightly update site URLs to be used w/ Eclipse 3.7 or JBDS 5.0:
* JBT 3.3 Nightly Trunk -
http://download.jboss.org/jbosstools/updates/nightly/trunk/
* JBT 3.3 SOA Tooling Nightly Trunk -
http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/
* JBDS 5.0 Nightly Trunk -
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk....
* JBDS 5.0 SOA Tooling Nightly Trunk -
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk....
publish SOA Tooling aggregate nightly / milestone sites onto
download.jboss.org
-------------------------------------------------------------------------------
Key: JBIDE-9029
URL:
https://issues.jboss.org/browse/JBIDE-9029
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Affects Versions: 3.3.0.M2
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.M3
I assume we'll do something like:
Core:
http://download.jboss.org/jbosstools/updates/nightly/trunk
SOA Tooling:
http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk
And, for the next milestone:
Core:
http://download.jboss.org/jbosstools/updates/development/indigo/
SOA Tooling:
http://download.jboss.org/jbosstools/updates/development/soa-tooling/indigo/
And, once it's available in JBDS, we'll composite the sites together here:
http://devstudio.jboss.com/updates/5.0/staging/
and
http://devstudio.jboss.com/updates/5.0/
Does that make sense?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira