I haven't taken a look at this closely (I had read Aaron Boodman's blog about the approach at http://www.aaronboodman.com/2009/07/bundling-multiple-versions-of-binary.html previously), but I am not sure this can detect all the cases we need to differentiate.
For example, on Fedora Core 10 FF3.0.11, the plugin needs to be linked against different libraries (the ff3+ entry there now), and it isn't clear how we can differentiate that in the JS stub from other FF3.0.11 builds that require the ff3 libraries. Also, given the other things that we need to get done for GWT 2.0 MS1, I am leery of making such a major change that might distract from getting those things done. So, my inclination would be to wait on this until after all the other OOPHM-related pieces are done for MS1 and if there is time left then we can pursue it further. I definitely do want to do away with all the different XPIs before the 2.0 release candidate, but I don't think that is a requirement for MS1. http://gwt-code-reviews.appspot.com/56808 --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
