Community
Participate
Working Groups
We were a little slow updating last milestone ... we'll do it right away this time. :) [In fact, certain advantage to doing so before "Sim. Release" deadline ... just in case found some unusual rare bug ... which, I would think extremely unlikely ... just saying it's best to.]. We are currently using version 3.11.0.v20150126-2015 (from M5) and our M6 version is 3.11.0.v20150317-0048.
I've noticed that "jdt.annotation" in our 'staging' area org.eclipse.jdt.annotation_2.0.0.v20140415-1436.jar org.eclipse.jdt.annotation_1.1.0.v20140129-1625.jar and current version from M6 is org.eclipse.jdt.annotation_1.1.100.v20140704-0625.jar org.eclipse.jdt.annotation_2.0.100.v20150311-1658.jar Should these be updated too? Any substantial changes?
Here's fix for jdt.core (after putting in eclipse-staging maven repo) http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=f8d2a2bab4e1020bedc849a802c925f8a11506e9 And, never mind about jdt.annotation. I see we have never put that in "staging" ... and, the thing I was looking at was for "eclipse-releases".
Reverted ... as temp work around for Bug 462783 - New certificate conflict http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=9ac444b64aabf1d18fa5532558d6cd0f579617b1
(In reply to David Williams from comment #3) > Reverted ... as temp work around for Bug 462783 - New certificate conflict > > http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > commit/?id=9ac444b64aabf1d18fa5532558d6cd0f579617b1 I've retriggered the build but it still fails with the same error: https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5096/console
(In reply to Andrey Loskutov from comment #4) > (In reply to David Williams from comment #3) > > Reverted ... as temp work around for Bug 462783 - New certificate conflict > > > > http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > > commit/?id=9ac444b64aabf1d18fa5532558d6cd0f579617b1 > > I've retriggered the build but it still fails with the same error: > https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5096/ > console Unfortunately, you may have to wait until a new "nightly" build is produced, which is where "pre-reqs" (such as parent pom) are "pulled from", I believe. One is scheduled for 8 PM (Eastern), but I can do one earlier if that would help you ... and others. Of course, would still take 2 or 3 hours to finish and update everything. ... would be around 4 PM Eastern?
(In reply to David Williams from comment #5) > (In reply to Andrey Loskutov from comment #4) > > (In reply to David Williams from comment #3) > > > Reverted ... as temp work around for Bug 462783 - New certificate conflict > > > > > > http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > > > commit/?id=9ac444b64aabf1d18fa5532558d6cd0f579617b1 > > > > I've retriggered the build but it still fails with the same error: > > https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5096/ > > console > > Unfortunately, you may have to wait until a new "nightly" build is produced, > which is where "pre-reqs" (such as parent pom) are "pulled from", I believe. > > One is scheduled for 8 PM (Eastern), but I can do one earlier if that would > help you ... and others. Of course, would still take 2 or 3 hours to finish > and update everything. ... would be around 4 PM Eastern? Would be cool if the results could be consumed in 2 or 3 hours from now.
(In reply to Andrey Loskutov from comment #6) > Would be cool if the results could be consumed in 2 or 3 hours from now. I started a new N-build at 1:00 Eastern. Assuming it completes without error, should be ready around 3:30 or 4:00 PM ... and, again, this is based on my limited knowledge of "the Gerrit builds". Others may know if something else needs to be done (or, even, if there is an easier way).
(In reply to David Williams from comment #7) > (In reply to Andrey Loskutov from comment #6) > > > Would be cool if the results could be consumed in 2 or 3 hours from now. > > I started a new N-build at 1:00 Eastern. Assuming it completes without > error, > should be ready around 3:30 or 4:00 PM ... and, again, this is based on my > limited knowledge of "the Gerrit builds". Others may know if something else > needs to be done (or, even, if there is an easier way). I noticed the "next" build failed too, that ran around 5 PM (after the N-build was complete). https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5097/ To write it down, in the hope it helps (some of us) to remember next time, a new N-build is probably part of the equation, but also, there is a job to "deploy parent pom" ... and is appears set to run once every 24 hours. https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.5/ I'd offer to try to do it "manually" now, but it's scheduled time appears to be midnight ... 20 minutes from now. I'm also intrigued, more a topic for original bug 462783, why "things work" for a few of the bundles it compiles, but then fails on the third one: eclipse.platform.ui ................................ SUCCESS [ 49.853 s] org.eclipse.core.commands .......................... SUCCESS [ 42.956 s] org.eclipse.core.databinding.observable ............ FAILURE [ 1.179 s]
(In reply to David Williams from comment #8) > I noticed the "next" build failed too, that ran around 5 PM (after the > N-build was complete). > https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5097/ *Next* build succeeded now, thanks David! https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/5098/
Ok, now that I have both jdt.core and apt deployed to our staging area, I am ready to try this again. Just to confirm is fixes original issue, if nothing else. Though, I know JDT wants another update "in a week or two" according to bug 462783 comment 3. Stephan, when you are ready for that update, just re-open this one, and I'll be glad to update again. (I am assuming that bug 371614 is not so bad that it will produce horrible results. Let me know if I misunderstand it's severity.). Changes to parent pom, to use M6 versions. http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=a22a66ad08a1607808b37952230ffb32480146b5 (I will start a local test build, to confirm it at least "works for me" ... would not effect Gerrit jobs, until after parent pom reployed, at midnight tonight).
Stephan, I see that bug 371614. But see that a similar bug 463320 was opened. So, let me know if I should update "now" (if bug 371614 was in last I-build) or, if I should wait for bug 463320 to fixed in an I-build. I'll re-open now, though, we we don't forget.
(In reply to David Williams from comment #11) > So, let me know if I should update "now" (if bug 371614 was in last I-build) > or, if I should wait for bug 463320 to fixed in an I-build. Bug 463320 isn't going for M5. But the other bug is the important one. But now that we are close to the next I build, we might as well wait for that, perhaps?
(In reply to Jay Arthanareeswaran from comment #12) > (In reply to David Williams from comment #11) > > So, let me know if I should update "now" (if bug 371614 was in last I-build) > > or, if I should wait for bug 463320 to fixed in an I-build. > > Bug 463320 isn't going for M5. But the other bug is the important one. But > now that we are close to the next I build, we might as well wait for that, > perhaps? Yes, will do. And, I know it's just a typo, but am sure you meant "Bug 463320 isn't going for *M7*". (Time flies, eh? :)
https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=3484d4cbc7f140d3900f7e8bd17b931ef9646352 Updated core and apt.compiler to versions from I20150408-1100.
