Community
Participate
Working Groups
Since we don't have cool "version checking tools" :) ... to sanity check 3.8 and 4.2, I unzipped the M7 candidate SDK in two directories, did a file list of "plugins" then did a "diff" of those file file listings. I'll attach an "annotated" list of the differences. Naturally many differences _are_ expected or relatively normal. But, some seem oddly different. Not sure if there's reason for concern (such as "getting wrong code") or if its a minor quirk of versioning and the comparator and the actual byte codes are exactly as expected. I sort of tired out annotating and analyzing after a while. But, thought I'd "post what I have" and perhaps others will know off the top of their heads what's normal, expected, and what deserves further attention. And, I'm thinking, in most cases we should be prepared to explain the differences ... I'm sure someone will eventually ask.
Created attachment 215038 [details] annotated list of differences I've marked some things as "expected differences" and some things as "questions" of differences .... and as I mentioned ... got tired so about last third of list I did not look at too closely.
Some answers... The only one that stands out to me as a genuine problem is Ant. Q: Shows what I know ... I thought "compatibility layer" was in 4.2? < org.eclipse.ui.workbench.compatibility_3.2.100.v20111007-1312 < org.eclipse.ui.workbench.compatibility.source_3.2.100.v20111007-1312.jar A: This is the old compatibility code between Eclipse 2.1 and Eclipse 3.0. Q: Not sure why Ant would be different? from January, to April? A: Yes this one looks weird to me. I would expect these to be the same. Q: 3.8: no core.boot in 4.2? A: Yes, core.boot was deleted in 4.2. Q: not sure why "comands" would be different .. by a few minutes? A: This bundle is split streamed (it is in platform UI for historical reasons). I suspect a commit was cherry-picked across several minutes apart. Expected. Q: databinding difference from 2011 November 7th and 9th? A: Same as above. Split streamed and the fix was probably committed on different days in the two streams. Q: runtime.compatibility.auth, and help appserver only in 3.8? A: Yes these bundle were intentionally removed from 4.2.
And, appserver only in 3.8 ? < org.eclipse.help.appserver_3.1.400.v20111004-1656.jar < org.eclipse.help.appserver.source_3.1.400.v20111004-1656.jar This isn't the first milestone's that's been removed, right? (I ask since from some initial "aggregation runs" looks like BIRT still depends on it ... and our repo has been kind of a weird combination of 3.8 and 4.2, until now. So, just wanted to confirm ... is there any "migration" notes about it? Thanks so much.
(In reply to comment #3) > And, > > appserver only in 3.8 ? > On IRC, Remy pointed me to bug 348410 comment 1, which was about 3.7/4.1 difference. ... Sounds like possibly could have been removed from 3.8, if thought about earlier? But, sounds like a history.
(In reply to comment #3) > And, > > appserver only in 3.8 ? > Yes, intentionally removed from 4.x. See the migration guide: http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/4.2/incompatibilities.html?h=R4_HEAD#help-appserver
I'm marking as invalid since these differences were accounted for (by slight timing changes in cherry picking and the like) ... well ... we hope. :)