I got used to a module system with versioning with the NetBeans Platform
and I was happy to see that since 6.9 they started a convergence and
today the NetBeans Platform module system has got a high degree of
compatibility with OSGi. I thought of myself in the OSGi camp since a
couple of years, even though I'm still less than a newbie (I had other
high priority things and I decreased OSGi priority as I see adoption
slower than I expected).
Yes, module system have got problems with the classloaders. But as far
as I see with the NetBeans Platform, they can managed. I think that the
more complex an application is, the higher the need for a module system
is. Take Hudson/Jeskins, for instance. At the beginning it was a piece
of cake to use and upgrade. Since more than one year every update
experience is a pain in the ass, because some plugin breaks. As far as I
understand, the Hudson/Jeskins plugins are versioned, but there's no
compatibility enforcing facility that could prevent me from installing
an incompatible plugin (and if there is such a facility, well it's
broken as I just upgraded Hudson and a plugin broke).
I can't imagine how to build an application with the complexity of
Eclipse or NetBeans or JDeveloper without a module system with enforced
versioning.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
