On Fri, May 9, 2008 at 12:01 AM, Jan Nielsen <[EMAIL PROTECTED]> wrote:
> FWIW, IMO introducing Spring and OSGI to replace a number of the > choices in Maven is a good start; these are excellent frameworks with > excellent documentation, excellent communities, and a lot of > experienced developers - something that simply cannot be said of > Plexus, "XBR", Classworlds - and that represents tremendous value. Not > recognizing, or acknowledging, that seems likely to be at the root of > Maven's slow progress. Java5+, including annotations and generics, is > a no-brainer, and it has been for a long time. On Fri, May 2, 2008 at 6:53 > AM, nicolas de loof < All good points Jan. Plexus is a pretty slick container so I can't imagine it would be that hard for it to adapt to OSGi. Following a standard is the best way to go almost always even if the non-standard solution is more superior. Alex > ---------------------------------- > > ] > > Note to plexus lovers : > > CONTROVERSAL PROPOSAL, please don't blame me and just give good > arguments ! > > [ > > > ---------------------------------------------------------------------------------------------------------------------------- > > ] > > > > Maven is built on Plexus. This lightweight container is used (afaik) for > : > > - simple (javadoc) annotation-based programming model > > - lifecycle management > > - dependency injection > > - classloader isolation for plugins (using classworld) > > > > Let's now consider the today responses to the same requirements : > > - Since Java5, annotations are common, and JSR-250 introduces standard > > annotations that can address some basic lifecycle and IoC requirements. > > - The IoC container ecosystem is dominated by Springframework. Maybe not > the > > best technical one for any reason, but the best documented and most know > by > > developers. > > - Classloader isolation is very well adressed by OSGi, with the advantage > of > > beeing a recognized standard, with many documentation AND business > interest. > > > > Maybe Plexus was a very advanced container when it was created, but it > did > > not become the today 1rst choice technology. > > > > Considering an opensource tool like maven is built by volunteers > developers, > > it would be a good thing to attract talentuous ones to use up-to-date and > > well known technologies. As an example, Archiva (trunk) is migrating to > > Spring as it's IoC container. > > > > Could we consider for future maven version (let's say 2.2, or "3.0" - as > 2.1 > > is allready in advanced development phase) to replace plexus with a > > combination of Java5 + Spring + OSGi ? > > > > Nicolas. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
