[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...
]
Nick Boldt commented on JBIDE-9029:
-----------------------------------
As long as users understand that when JBT Core drops, the SOA Tooling stuff may or may not
be available.
Added complication is that when I move the development/ site from, say, M2 to M3, I'll
have to remove the previous SOA Tooling stuff if it's not compatible with the current
Core stuff. Otherwise you could end up with a site that contains:
* JBT Core 3.3.0.M3
* JBT SOA Tooling 3.3.0.M2
And I suspect that's a bad idea...?
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