[jbosstools-issues] [JBoss JIRA] (JBTIS-28) migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/

[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated JBTIS-28: ---------------------------- Description: JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo. However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example. So, either you * need to publish a site from which these can be resolved [1] ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2]. ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4] [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/ [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration... [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd Both options would work... but I suggest that building a new aggregate might be better. If you agree, you'll want to therefore migrate the code in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to a folder under https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... was: JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo. However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example. So, either you * need to publish a site from which these can be resolved [1] ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2]. ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4] [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/ [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration... [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira