[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9029: -------------------------------------------- "On updatesites we do a compositecontent split <root>/soa <root>/core (names to be decided) We do that for both jbt and jbds In JBT: we do the updatesite split for composite-component In JBDS: we create two features: JBoss Developer Studio Web JBoss Developer Studio SOA Pack (for those wanting to install sub-features they can use the "uncategorized option" which we currently would not say is fully supported)" Meaning we would have something like: Core: http://download.jboss.org/jbosstools/updates/nightly/trunk/core SOA Tooling: http://download.jboss.org/jbosstools/updates/nightly/trunk/soa combined: http://download.jboss.org/jbosstools/updates/nightly/trunk/ Core: http://download.jboss.org/jbosstools/updates/development/indigo/core SOA Tooling: http://download.jboss.org/jbosstools/updates/development/indigo/soa combined: http://download.jboss.org/jbosstools/updates/development/indigo For JBDS its separate locations too and merged into the main site. The "extra" in JBDS is that there will be a SOA and Core feature for easy/restrained updates. Its SOA's tasks to ensure what gets "aggregated" into the core sites are consistent (i.e. compatible) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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...? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBIDE-9029: ------------------------------------------ Isn't the whole idea of splitting this stuff up so that the SOA tooling can update on a separate schedule from JBDS Core? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9029: ----------------------------------- FYI, here are the build folders for JBT-SOA and JBDS-SOA: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/ http://svn.jboss.org/repos/devstudio/trunk/product/soa-site/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9029: ----------------------------------- New view: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/SOATooling/ New jobs: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/SOATooling/job/jbos... http://hudson.qa.jboss.com/hudson/view/DevStudio/view/SOATooling/job/devs... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-9029 at 6/14/11 6:28 PM: ------------------------------------------------------------ JBoss Tools - SOA Tooling results: Build results for specific builds: http://download.jboss.org/jbosstools/builds/nightly/soa-tooling/trunk/ Latest build (refreshed every build): http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... Latest nightly update site (refreshed every build): http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ --- JBDS - SOA Tooling results: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... was (Author: nickboldt): JBoss Tools - SOA Tooling results: http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.... JBDS - SOA Tooling results: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9029: -------------------------------------------- moving of M2 since SOA is removed from main site and SOA fixes can be done in M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9029?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9029: --------------------------------------- Fix Version/s: 3.3.0.M4 (was: 3.3.0.M3) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira