Community
Participate
Working Groups
We are currently on M3 version. Updating each milestone is to better test the compiler. Seems sooner the better in the rare event something surprising happens. Assuming no major or incompatible change, this is just a matter of swapping in the one jdt.core bundle in current base builder.
Update basebuilder (in Git, master) to contain org.eclipse.jdt.core_3.9.0.v20121025-162051.jar and removed org.eclipse.jdt.core_3.9.0.v20121208-144805.jar and tagged it with R38M6PlusRC3E I also updated the scripts in eclipsebuilder (master) to use this new tag R38M6PlusRC3E instead of the previous R38M6PlusRC3D. (There's two critical files, masterBuild.sh and getBaseBuilder.xml, also a couple of test scripts I went ahead and updated to "E"). I tested "checkout" with getBaseBuilder.xml on my local machine and it contained the new jdt.core. For the record, I did make a typo while tagging and created R38M6PlusCR3E, instead of "RC", but decided to go ahead and leave it, in addition to the correctly named R38M6PlusRC3E, that it shouldn't be that confusing to anyone and even obvious it is tagging the same commit.
I should note, this same version will be used for Juno maintenance builds (3.8.2 and 4.2.2), unless someone says we can't/shouldn't do that.
