JavaXPCOM: split MozillaInterfaces.jar into two separate libraries
Javier Pedemonte <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.java |
|---|---|
| Message-ID | <koOdnfprm-ahrtzYnZ2dnUVZ_tGdnZ2d__37841.405082918$1161900970$gmane$org@mozilla.org> |
Several weeks ago, I checked in the patch for https://bugzilla.mozilla.org/show_bug.cgi?id=328901, which splits the MozillaInterfaces.jar library into two separate libraries: (1) MozillaGlue.jar contains the main Mozilla class and all the other 'helper' classes; (2) MozillaInterfaces.jar now only contains the generated Mozilla interfaces. This change has only been made on the trunk (i.e. XULRunner 1.9), but I will probably make the same change on the 1.8 branch. This change was made for several reasons. For one, it provides a better separation of the code. MozillaInterfaces.jar contains all of the generated interfaces, both frozen and unfrozen. So particularly for unfrozen and new interfaces, that library is specific to a given release. Whereas the classes in MozillaGlue.jar should remain mostly static through releases (except for new features). That's the plan, anyway! Secondly, this separation helps out with the Java Component Loader work (https://bugzilla.mozilla.org/show_bug.cgi?id=299263). The Loader generates the Mozilla interfaces on the fly, so it only needs to load MozillaGlue.jar and can do without the much larger MozillaInterfaces.jar. javier pedemonte