> I actually think jamming all this into the JDK is a very
> bad idea ...

Yes, I also strongly second this. What I ment was: OWB will need nothing more 
than a simple JRE and doesn't need additional J2EE libraries as it is defined 
in the JSR-299 Spec. 
All the headers are in javax.inject which hopefully will get the standard in a 
few years.

LieGrue,
strub

--- Jason van Zyl <[email protected]> schrieb am Fr, 1.5.2009:

> Von: Jason van Zyl <[email protected]>
> Betreff: Re: AW: Usage of spring (or better, the not so usage of spring)
> An: "Maven Developers List" <[email protected]>
> Datum: Freitag, 1. Mai 2009, 16:41
> 
> On 1-May-09, at 12:48 AM, Mark Struberg wrote:
> 
> > 
> > A little bit of self advertisement:
> > 
> > why not consider OpenWebBeans [1]?
> > 
> 
> You can work on whatever  you like, you have access to
> a sandbox.
> 
> Personally nothing interests me except XBR and Guice.
> Ultimately in two years it's not going to matter, there will
> be some standard annotations and the decision about what is
> underneath running is really not going to matter.
> 
> > 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.
> > 
> 
> I actually think jamming all this into the JDK is a very
> bad idea and has done nothing but hamper Java. There's
> nothing wrong with a small library you have to add to an
> application.
> 
> > 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]
> > 
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/SonatypeNexus
> http://twitter.com/SonatypeM2E
> ----------------------------------------------------------
> 
> In short, man creates for himself a new religion of a
> rational
> and technical order to justify his work and to be justified
> in it.
> 
>   -- Jacques Ellul, The Technological Society
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to