Currently experiencing cascade failures insofar as components that
depend on other components are failing because their upstream are failing.
All red jobs:
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indig...
---
Here's the problem stack - looks like some refactoring last week (moving
stuff from Central to Examples) might have caused some havoc to
components that depend on these shared classes.
common: test failure
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
WS: compile failure
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
Runtime: compile failure
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
Examples: SVN checkout failures for vmg19-rhel5-x86; slave disconnected,
reported to ci-issues@, and we're respinning.
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
Portlet: compile failure
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
Maven: compile failure due to project examples
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
Central: compile failure
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(Also failing in trunk:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cen...)
JBT Aggregate: missing o.j.t.maven.jpa feature due to upstream maven
component failure
ESB, SOA Tooling: blocked by upstream.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com