Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #336544 +++ Bug 336544 talks about fixing a serious bug in the JDT compiler, which could lead to incorrect bytecode being generated. TM should adopt the new compiler by upgrading to basebuilder r36x_v20110209, such that invalid byte code is avoided.
resolved fro 3.2.2rc4
It turned out that due to bug 337053, I will have to re-tag 2 features. This re-tagging also brings up the question whether any of the bundles need to be re-tagged due to the compiler change (similar to bug 336815 and bug 336780). We haven't been using the comparator in the TM project so far, so I don't know how to run it against my repositories to find out whether any bundles need retagging. Could somebody else help out and run the comparator for us? I'd also like to get confirmation that any bytecode changes due to the new compiler are appropriate. For investigation, zipped repos are available: - The new build with the r36x_v20110209 basebuilder: http://download.eclipse.org/tm/downloads/drops/M20110212-1700/tm-repo-M20110212-1700.zip - The previous build with the R36_RC4 basebuilder: http://download.eclipse.org/tm/downloads/drops/M-3.2.2RC2-201102011000/tm-repo-3.2.2RC2.zip
Olivier Thomann was kind enough to verify the TM build with the new compiler, and it looks good (see bug 336544 comment 31). For 100% reproducable builds I should usually re-tag org.eclipse.rse.services but since Helios SR2 is already starting its "quiet week" I think I'll not do that and just rename the existing M-build (since the change is trivial in the bytecode). Thanks again Olivier for checking - issue resolved.
