| Re: [atf-dev] JavaXPCOM ownership |
|
Good point Olivier. >From ATF standpoint, we would very much want to keep JavaXPCOM where it is now, in XULRunner builds and as part of Mozilla core. This extremely simplifies XULRunner adoption, because adopting project (we, Olivier) don't have to worry about matching JavaXPCOM to XULRunner versions and users have just one package to download (will have, once bug https://bugzilla.mozilla.org/show_bug.cgi?id=507575 is fixed). In Eclipse it's already difficult to adopt XULRunner, because of licensing issues it can't be packaged with Eclipse projects like ATF. I breifly looked at existing JavaXPCOM bugs (about 35 of them), however I didn't run into any bug that would be clearly caused by JavaXPCOM. The biggest issue that we suffer from is XULRunner crashes lead to whole Java Virtual Machine crashes. This complicates the development and makes it difficult to package ATF with other Eclipse projects, because there's nothing worse than crashing application. On the other hand we can't easily switch from one Java-XULRunner bridge to other because we tightly depend on current API. I would love to see JavaXPCOM implemented in such way that there would be no crashes while keeping it's API unchanged. So there's definitely a room for experimentation! I'm willing to contribute towards all that tasks, that is keep JavaXPCOM bridge simple to adopt as it is now, make it more resilient to failures, keep existing APIs. Benjamin, how can we proceed now? Olivier, do you see similar issues with JavaXPCOM as we in ATF? would you like to investigate together any of areas mentioned by Benjamin? cheers Jacek Olivier Rossel wrote: [Originaly posted on the mailing-list atf-dev] [Cross-posted on the mozSwing mailing list] I base my projects on JavaXPCOM and the disappearance of that project would be extreme bad news. Please discuss the details of the new status of JavaXPCOM publicly (on this list or on any other public medium) so users can provide feedback. On Saturday, September 5, 2009, Jacek Pospychala <jacek.p@xxxxxxxx> wrote:hi Benjamin, I step in to maintain JavaXPCOM. I very appreciate Javier's work and it's absolutely worth continuing. To not mention it's fundamental role in ATF existence, there's also a variety of other projects that also depend on it. Since it's friday night here, let's discuss the details the coming week, I'll get in touch with you. Jacek Benjamin Smedberg wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear ATFers, As the primary clients of Mozilla's JavaXPCOM technology, I'm looking for nominations/volunteers for somebody to be maintainer of the JavaXPCOM bridge. Javier Pedemonte was formerly the module owner of JavaXPCOM in the Mozilla code. As far as I know, Javier is no longer available to maintain this code (he hasn't responded to the emails I've sent). As part of Mozilla's ongoing work to streamline our codebase and make it easier to maintain, we're planning on removing JavaXPCOM from the Mozilla core and have it be maintained as a separate project. I'm afraid that future releases of Mozilla/XULRunner will happen without a JavaXPCOM project and tools such as Eclipse which use JavaXPCOM will be stuck on older versions of Mozilla. If there were an active owner, I'd also like to explore other ways that Java could embed Mozilla without the complexity and instability from the JavaXPCOM bridge: perhaps something more like a Java<->_javascript_ bridge or reusing the Java<->NPAPI bridge to extract information from Mozilla in a more stable way. - --BDS -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKoWRdSSwGp5sTYNkRAltxAKCTdY9YPj7ehz8JUVNtOsETf+4zSwCfdBh+ o+xYt573mnpvtroO+GY+qZc= =dIq/ -----END PGP SIGNATURE----- _______________________________________________ atf-dev mailing list atf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/atf-dev _______________________________________________ atf-dev mailing list atf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/atf-dev_______________________________________________ atf-dev mailing list atf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/atf-dev |