[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9029) publish SOA Tooling aggregate nightly / milestone sites onto download.jboss.org

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605627#comment-12605627 ] 

Nick Boldt commented on JBIDE-9029:
-----------------------------------

We can do things case-by-case if it's not possible to validate that JBDS-Core milestone X is compatible with JBDS-SOA milestone X-1 during the time while milestone X is being developed. If it's found incompatible, we can decide then what to do -- remove it, leave it, document it... 

It's easy enough to add/remove stuff from a composite. The bigger issue is the user experience.

In theory, the whole site should be installable w/o special "don't install that version, use the older one" instructions.

Failing that, we either have segregated sites for Core and SOA, which are never combined, or we ensure that there's always a compatible "release train" JBDS-SOA build (even if rough) available at the time that JBDS-Core drops its site, so that the complete set of features can be updated all in one go (then the SOA bits can be updated AGAIN, if needs be).

This is more about managing timelines than anything else. :)

> 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