Nope, just me (just kidding). The current
"visible" problem is with EclipseLink but ... just so everyone
else knows what we (don't) know ... we've exchanged some notes and something
"mysterious" is going on. Current theory is that "mylyn's"
whole repo is missing ... waiting to hear from them ... here's the exchange
so far ... if anyone has recently removed ejb_3.1.0
from their repo, can you let us know?
> > David,
> > I'm curious why this is happening now. This same build has been
> > submitted since last Thursday or Friday, and is only failing
> > After review it looks legitimate and we are investigating what
> > should do about it, but the issue looks like it had been masked,
> > I'm wondering if the masking is permanently removed, or if this
> > failure will in essence be temporary.
> > The problem is that we aren't building our repo with the ejb_3.1.0
> > dependency (we don't put it in plugins and the features don't
> > upon it - but a jar would depend upon the classes. The jar in
> > question is a special case though as it would only be used in
> > container where the classes already exist - so actually shipping
> > jar would be superfluous).
> > -Eric
> Hmm, not sure ... it could be you
(or, aggregator) was "picking it
> up" from someone's else repo and they have changed their repo.
> And, I think Mylyn's repo is currently "not present at all".
> this sound like the kind of think that Mylyn might have in their repo?
Jeff Johnston <jjohnstn@xxxxxxxxxx>
Cross project issues
06/13/2012 11:34 AM
Failures in the Hudson Juno run.aggregator
I noticed that the Juno run.aggregator job is failing
on Hudson after a
bunch of RC4 changes. Is someone assigned to each of the issues (other