Well, I think we have to rebuild them again because of a different dependency error in the modeling package. I prefer to have a clean build based on the content in /releases/staging anyway, but didn't have the time to look into it today so far.
Regards, Markus On Thu, Mar 22, 2012 at 14:29, Ed Merks <[email protected]> wrote: > David, > > Thanks! > > No, I don't think Xcore is part of the Modeling package (yet) nor any > other EPP package I know about, so I suppose those won't need to be redone. > > Cheers, > Ed > > > > On 22/03/2012 1:51 PM, David M Williams wrote: > >> Well, normally I'd say "no" .... but, by virtue of meritocracy, when Ed >> says we should, I believe it! >> >> Note that no downstream clients are affected >>> >> What about EPP? I assume this effecting modeling package? But only >> modeling >> package? >> >> So, at the moment, I'll say "yes" and plan on starting a new aggregation >> build at 9 AM Eastern. This will give a few minutes for anyone object, >> >> That respin will be complete about 11 AM Eastern I think that means the >> EPP packages will be re-done by approx. 4 PM Eastern. It'll make it a late >> day for some ... not much time to mirror ... but still in time for >> EclipseCon. >> >> This all assume everything goes smoothly .. no one has broken their >> repo ... hudson stays up ... etc. >> >> Thanks, >> >> >> >> >> >> >> From: Ed Merks<[email protected]> >> To: Cross project >> issues<cross-project-issues-**[email protected]<[email protected]> >> >, >> Date: 03/22/2012 08:16 AM >> Subject: [cross-project-issues-dev] Respin for Xcore >> Sent by: >> cross-project-issues-dev-**[email protected]<[email protected]> >> >> >> >> Hi, >> >> I wanted to beg and grovel for a respin to pick up the 1.0.0M6a build of >> Xcore. Changes in the base framework results in a flood of errors in the >> log just hovering over the Xcore editor and it breaks the hovers that >> should come up >> >> https://bugs.eclipse.org/bugs/**show_bug.cgi?id=375028<https://bugs.eclipse.org/bugs/show_bug.cgi?id=375028> >> I spent all day yesterday addressing this an another problem, but I failed >> to notice that my git push failed. As a result, the changes weren't >> picked >> up for the M6 build yesterday. >> >> My EclipseCon presentation next week demonstrates this and it would be >> very >> sad if folks trying it for themselves have these kinds of problems. >> >> Note that no downstream clients are affected, so there's risk of >> unintended >> consequences. >> >> Regards, >> Ed____________________________**___________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@**eclipse.org<[email protected]> >> https://dev.eclipse.org/**mailman/listinfo/cross-**project-issues-dev<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> >> >> ______________________________**_________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@**eclipse.org<[email protected]> >> https://dev.eclipse.org/**mailman/listinfo/cross-**project-issues-dev<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >> > ______________________________**_________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@**eclipse.org<[email protected]> > https://dev.eclipse.org/**mailman/listinfo/cross-**project-issues-dev<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> >
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
