My vote http://code.google.com/p/google-guice/issues/detail?id=366
On Wed, Jun 30, 2010 at 6:25 PM, Max Bowsher <[email protected]> wrote: > On 30/06/10 20:57, Sam Berlin wrote: > > A small status update on releasing a new version... > > > > Still needs to be done: > > - Bob needs to spend some time reviewing the changes. > > - Wiki needs to be updated to reflect a Guice 3.0 world. > > - @since tags need to be added or modified. > > - Dhanji wants to include the new guice-persist & a servlet fix, but > > they aren't true blockers for a release (just awesome additions). > > - some recent issues: 507, 508, and 509. > > - audit old issues to make sure there's nothing blocking (I don't think > > there is). > > > > Decided: > > - Everyone is OK (so far) with a version number of 3.0. > > - JIT providers / autobinders / etc.. will not be in the 3.0 release. > > - Refactoring the internal package is shelved, in favor of a solution > > that will hide the package from IDE autocompletions (at which point we > > can refactor at will in internal). > > > > That sound about right? > > Doesn't _have_ to be done before the release but would be nice: > * get some Maven2 pom.xml files sorted, and ideally into trunk this time. > > I'd be happy to work on that and suggest we simply aim to have minimal > POMs suitable for submitting the built jars to the maven repository - > punt on any thoughts of making the POMs good enough to assist in > generating Eclipse or other IDE projects for now. > > > Oh, and also: > * Can we include a guice-grapher jar in the 3.0 release? > > Max. > > -- You received this message because you are subscribed to the Google Groups "google-guice-dev" 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-dev?hl=en.
