The Politics of OSGi and JSR 277

Things seem to be heating up around the compatibility between OSGi and JSR 277, in particular the different version numbering schemes. Peter Kriens, Alex Blewitt provide some good commentary for the OSGi scheme and Stanley Ho defends the proposed JSR 277 scheme.

However, Hal Hildebrand, the Oracle OSGi guru, provides the best insight into what is wrong with JSR 277: politics. For all Sun’s executive-speak about being a hip open company, they continue to behave like an old fashion hardware vendor. The non-existent JSR 277 expert group is a mockery of the JCP process and by anyone’s definition of openness. Instead of trying to create a community and build bridges between JSR277 and OSGi, Sun is using backroom tactics to find some type of ‘compromise’ between OSGi and JSR277.

Sun stop the bilateral discussions, re-boot the JSR 277 expert group with a real spec leader and start participating in the OSGi organization. In short stop the politics and start a real open discussion to ensuring OSGi and JSR 277 are compatible.  Anything else is just going to be bad news for Java.

9 thoughts on “The Politics of OSGi and JSR 277

  1. Testify brother, testify! 😉

    All joking aside, I’ve heard similar things from folks outside of IBM…which really is a shame, because OSGi provides compelling value to customers.

    I have been making a concerted effort to not disparage any vendor for exerting control over “a community”…but I really expected Sun to act differently now that they are “a hip open company”….and “open to possibilities” (quoting a Sun slogan).

  2. “outside of IBM” => Ian doesn’t work for IBM. He works for the Eclipse Foundation, which, although it is partially funded by IBM is independent of it.

  3. I cannot really understand how Sun can claim that Java is so important to them. The say they wanna work together with the community, but at the same time let politics interfere with such an important JSR! This is about the future of the Java Platform, because IMHO JSR 277 changes the whole game of how to approach writing Java applications!

  4. Put that way, what you’re saying is “just validate OSGi as the standard for Java Modules”, right?

    Where does that leave companies that need 4 digits schema like, for example, IBM (which uses a 4 digit version schema for DB2 and Websphere)?

Comments are closed.