[
https://issues.jboss.org/browse/JBIDE-12038?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12038:
------------------------------------
As we discussed today the problem was that the parent pom was changed to add the soa tests
site as a dependency when building ANY project for which swtbot tests were enabled. Having
reverted that we seem to be in a better place.
But I wonder, should we also remove the rest of the "turns itself on
unexpectedly" profile, jbosstools-staging-aggregate-soa-tooling, which will
unexpectedly inject jbosstools-nightly-soa-tooling as a repository from which to resolve
deps (potentially newer ones than you want) ? Yes, I think so.
Especially since Core builds shouldn't have that site enabled or we DO end up with a
circular dependency :)
I've removed the offending profile from branch and trunk.
Setting up Jenkins for 3.4 - breaks ESB Bot tests
-------------------------------------------------
Key: JBIDE-12038
URL:
https://issues.jboss.org/browse/JBIDE-12038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: SOA Tooling
Affects Versions: 3.3.0.Beta3
Reporter: Len DiMaggio
Assignee: Nick Boldt
Fix For: 3.4.0.M1
http://hudson.qa.jboss.com/hudson/job/soatools-3.3.0_Nightly.component--e...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira