[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9029) publish SOA Tooling aggregate nightly / milestone sites onto download.jboss.org
[
https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9029:
------------------------------------------
I'm suggesting that the SOA update site should work with what's been released
(i.e. latest milestone or release), but it should happen release-train-ish, with JBDS
releasing a milestone that we can test/rebuild against, then SOA validates, etc. We need
to check with John however to see if that's what he was thinking. We're starting
to get to where the rubber meets the road and will need some way to keep in sync...
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: Nick Boldt
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