Not sure if this was a tongue-in-cheek comment, but I'd personally go with native OSGi support at first. I don't know how many years it will take before a majority of Java installations are migrated to Java 7. If Sun's module system is really compatible with OSGi, then we shouldn't have to worry.
alex On Wed, May 7, 2008 at 9:39 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > Let's not forget that Java has its own module system, which will appear in > JDK 7 (JEE 6). Sun does promise compatibility with OSGi: > > http://www.infoworld.com/article/08/05/07/Java-platform-to-get-modularity-OSGi-support_2.html > > Assaf > > On Tue, May 6, 2008 at 12:04 AM, Tal Rotbart <[EMAIL PROTECTED]> wrote: > > > +1 OSGi is becoming an buzzword :-) > > > > On Tue, May 6, 2008 at 3:58 AM, Alex Boisvert <[EMAIL PROTECTED]> > > wrote: > > > +1 I see OSGi being adopted across all the major appservers. > > > > > > alex > > > > > > > > > On Sat, May 3, 2008 at 3:47 PM, Assaf Arkin <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > Downloading OSGi packages with dependency and version meta-data, > using > > > > that > > > > in the build, and creating packages that contain the right OSGi > > meta-data > > > > and can be used for deployment and runtime. > > > > > > > > I'm wondering if this is something we should put as a priority for > the > > > > next > > > > major release, 1.4: > > > > > > > > +1 Yes, please, the sooner the better. > > > > 0 Don't care either way. > > > > -1 No, we have better things to do. > > > > > > > > Assaf > > > > > > > > > >
