[
https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s...
]
Martin Malina commented on JBTIS-28:
------------------------------------
We've had the soa profile in tests/pom.xml because we didn't want to build/run
those plugins - remember they were mostly non-working in master, soa plugins were active
in 4.0.x branch. Now soa tooling development moved to master/kepler, so this can be
revised. BUT ... we're in the process of splitting the soa test repo, so it's not
worth bothering with it now. Maybe at least to make the build work we could remove the
soafeature for now?
produce a JBTIS unit tests update site (aggregate or composite)
---------------------------------------------------------------
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/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...
--
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