]
Martin Malina commented on JBIDE-13709:
---------------------------------------
I asked [~apodhrad] and he says currently they are testing with jbosstools-4.0.x so they
don't use this anyway. And when the time comes for them to start using Kepler
(master/jbosstools-4.1.x) hopefully they'll have their own update site and/or git repo
by then - that should be done in JBIDE-12974 I think.
So I will go with "disable those tests" right now - disabling esb test for now
and trying to use my fork in the build.
integration-tests should use JBTIS target platform to resolve
SOA-related requirements like Zest
------------------------------------------------------------------------------------------------
Key: JBIDE-13709
URL:
https://issues.jboss.org/browse/JBIDE-13709
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: esb, testing-tools
Affects Versions: 4.0.0.Alpha1-SOA
Reporter: Nick Boldt
Assignee: Martin Malina
Fix For: 4.1.0.Alpha2
From JBIDE-13594, but for integration-tests instead of esb project.
[~mmalina] said:
{quote}
I can still see the same error in a build from 03/01
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
{code}
[ERROR] Missing requirement: org.jboss.tools.esb.project.ui
1.5.300.Alpha1-v20130128-1848-B1149 requires 'bundle org.eclipse.zest.core 0.0.0'
but it could not be found
{code}
{quote}
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
requires ESB, which requires Zest.
So, you need to ensure you're building your integration stack tests (which
incidentally should be separated from the Core tests) using [~leacu]'s target platform
for JBTIS.
Here's how you patch your root pom (in the 4.0.x branch) to use the JBTIS TP (for
Juno-based requirements):
https://github.com/jbosstools/jbosstools-esb/pull/24/files
I'm not sure what you'll have to do for the Kepler-based tests - either need a
Kepler-based TP for JBTIS, or to disable those tests.
--
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: