[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/...

[Nick Boldt (JIRA)]

Nick Boldt created JBTIS-28:
-------------------------------

             Summary: migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/...
                 Key: JBTIS-28
                 URL: https://issues.jboss.org/browse/JBTIS-28
             Project: JBoss Tools Integration Stack
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: distribution, ESB, releng, target-platform
    Affects Versions: 4.0.0
            Reporter: Nick Boldt
             Fix For: 4.0.0


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/jbosstools/site/compositeArtifacts.xml
[3] http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/ 
[4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbosstools/site/ 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