Optional inject is a key missing part of the JSR. Agreed that the spec is way too immature. Is anyone moving the javax.inject spec since last year?
+1 on doing a release, but for a different reason. It would be nice not to have to play the classpath dance (ex. testng) in order to coexist with a version of guice since a year ago. I have personally lost hours and also lost time from other developers on jclouds due to using post-2.0 guice over classpath woes. In retrospect, using post 2.0 guice was a very bad decision, but to be fair, one shouldn't really ever zero releases in over a year from an staffed open source project. Those who use dependency managers such as maven are better off when there is a stable (if even marked beta, r1, r2, etc.) release in a public repository. Other google projects such as guava are probably also used inside the company, yet still allow the public the benefit of interim releases. my 2p. -Adrian On Mon, Jul 19, 2010 at 9:00 AM, Brian Pontarelli <[email protected]>wrote: > I think he made his point pretty clear actually. > > I'd agree that having all of these items covered are required for support. > However, the JSR doesn't provide a standard configuration mechanism and many > other pieces that are required to actually use DI in a project. Therefore, > implementing the JSR only gets you part of the way there. You still need to > bind everything using Guice modules or Springs Configuration (either XML or > classes). Unless you are building a library/framework that will be used > outside of your organization, you would probably be better just using > Guice's @Inject for now. > > -bp > > > On Jul 19, 2010, at 5:58 AM, Peter Reilly wrote: > > > Your point? > > > > Peter > > > > On Mon, Jul 19, 2010 at 12:28 PM, mortench <[email protected]> wrote: > >> it is not only about providing downloads. It is about fully > >> implementing javax.inject 100% (does it?), documenting how the > >> javax.inject implementation works (anything there ?) and about being > >> production-stable (nightly's very seldom are) ? > >> > >> Until you can say yes to all 3 things, I stand by my definition of > >> javax.inject not being supported by google guice. > >> > >> /Morten > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "google-guice" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > [email protected]<google-guice%[email protected]> > . > >> For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > >> > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > "google-guice" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > [email protected]<google-guice%[email protected]> > . > > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-guice%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
