Hey all,
I've been trying to get our internal changes out, and I"m now making
progress and exporting. This is in anticipation of a release of guice
real-soon-now. The main thing after these changes are exported is to
restore the maven build (which seems to have been borked by our upgrade
to ASM4, and I just haven't had a moment to fix it… Stuart - you are
invited to help with that. :D) Also, if there are any patches, fixes,
suggestions people want to get in before a new Guice release, once I
sync us all the way (today and/or tomorrow), please start speaking up.
That said, the goal is to release more frequently, even simply point
releases with minor fixes, so we can get out of this every-two-year
thing. Guice is relatively stable, but we're trying new things with
Dagger, and some of those things may be useful in Guice. Additionally,
the widespread deployment of Java7 and the forthcoming Java8 may prove
to have worthwhile advantages to consider, so by no means is Guice,
however stable, a done deal.
I want to thank everyone for being so patient while we ramp this up.
We're addressing a lot of internal usage issues in Google, partly by
tooling, partly by using Dagger where its use-cases are compelling,
partly by improving Guice to be tighter, detect error earlier, etc.
That internal work has meant we haven't been as external with our
changes and directions as we would, perhaps, have preferred. But there
are now plural full time staff charged with working on Dependency
Injection in Java inside Google plus a cadre of 20% timers. This should
mean love for Guice as well as new efforts.
That said, I also want to plug the project error-prone.
(https://code.google.com/p/error-prone/). It treats certain software
errors as compiler errors, and we (Sam B) have started down the road of
adding certain degenerate guice usage patterns as error-prone errors.
That stuff isn't exported yet, but I encourage people to use it. Its
like a tighter, more narrowly-focused find-bugs, and they've taken great
effort to make sure that they really are "errors." not warnings to be
ignored. We plan on doing some detection of common problems in
dependency-injection code as error-prone compiler errors. So check it
out folks.
In the mean-time, let's get the march to a 3.1 or 4.0 (still figuring
that one out) started!
sincerely,
Christian.
Christian Gruber :: Google, Inc. :: Java Core Libraries :: Dependency
Injection
email: [email protected] :::: mobile: +1 (646) 807-9839
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
