A little bit of self advertisement: why not consider OpenWebBeans [1]?
It is a best of all worlds approach, will get the official Java standard for dependency injection and is an Apache project (so no worry about licensing issues). OpenWebBeans extends the spec in the way that it also can be used in a purely JDK environment. So we have already moved out all JSF, JPA, EJB, JMS stuff into plugins which get picked up automatically if they are in the classpath. If not, OpenWebBeans will have no dependencies to any J2EE stuff, ServletContext etc! Checkout the latest sources from [2] Apache SVN. LieGrue, strub [1]http://incubator.apache.org/openwebbeans please note that M2 have changed heavily and is much more modular! [2] https://svn.apache.org/repos/asf/incubator/openwebbeans/trunk/ --- Nick Stolwijk <[email protected]> schrieb am Fr, 1.5.2009: > Von: Nick Stolwijk <[email protected]> > Betreff: Usage of spring (or better, the not so usage of spring) > An: "Maven Developers List" <[email protected]> > Datum: Freitag, 1. Mai 2009, 3:48 > > We're never going to use Spring > > I don't want to get myself in the discussion about the > blogpost or the > Sonatype / Maven discussion, but the above sentence caught > my > attention. I have searched the mailinglist but haven't > found any > discussion about the usage of spring and I was wondering, > why not > Spring? > > With regards, > > Nick Stolwijk > ~Java Developer~ > > Iprofs BV. > Claus Sluterweg 125 > 2012 WS Haarlem > www.iprofs.nl > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
