On Apr 25, 2008, at 4:46 PM, Richard S. Hall wrote:
Sam Pullara wrote:
The vast majority of people that are going to use this system will
have never heard of OSGI nor care about any of their more subtle
features and just want an easy way to leverage the vast amount of
libraries available (virtually all of them are not OSGi modules
today but are jar files in maven repositories). We shouldn't be
specing out some sort of uber container but rather a simple way to
tie code to its dependencies.
If this is all that people wanted, then we could just define
repositories and associated metadata and forget about all runtime
modularity support, but I strongly disagree that this is all people
want or else there wouldn't be such an upsurge in OSGi interest and
adoption.
I guess that is what I am arguing for. I don't see the critical need,
outside the internals of application servers and a very few plugin
based tools, for runtime modularity support. And if OSGi can load a
JSR-277 module then I feel like the interoperability job is done.
Sam
