Looks like the currently running aggregation
got both changes and it passes verification for me locally, so hopefully
the mirroring will succeed and it will be finished about 5:00 and I hope
to be back to my computer about 5 to promote new build to staging.
So ... if anyone needs a respin after
#534 (within an hour or two of it finishing) please let us know here on
this list. In other words, I'm assuming we'll be done by 5 PM Eastern,
but suspect we could stretch that to 7 or so if someone has a legal file
to fix or similar.
Eric Gwin <eric.gwin@xxxxxxxxxx>
06/13/2012 03:03 PM
Fw: Failures in the Hudson Juno run.aggregator
I've contributed a new repo. should resolve the issue.
On 13/06/2012 11:50 AM, David M Williams wrote:
Update ... Eric said to temporarily
disable EclipseLink, and he'll try to rebuild to avoid this dependency
... we'll see who shows up next.
[FYI, it is helpful, if you get a not about your project failing, to keep
us all informed, here on cross-project list. I know many are waiting for
a "green build"].
----- Forwarded by David M Williams/Raleigh/IBM on 06/13/2012 11:48 AM
project issues <cross-project-issues-dev@xxxxxxxxxxx>,
[cross-project-issues-dev] Failures in the Hudson Juno
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
> 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?