On 11 Dec 2012, at 19:09, Stuart McCulloch wrote:
The relevance was that I wanted to make sure any lifecycle providers
(including sisu) had whatever APIs they needed to do things effectively.
On 11 Dec 2012, at 23:44, Christian Gruber wrote:
If you're talking about Sisu-Guice then this is our minor branch of
Guice that has various patches that we've found useful in production,
but which have not yet been merged into Guice for various reasons. You
can see the individual patches in
https://github.com/sonatype/sisu-guice/tree/master/PATCHES along with
their upstream issue numbers. Note that you can use Sisu with
mainstream Guice if you want - you'd just need to build Guice from
master, as Sisu uses the ProvisionListener API that was added after
3.0
Ah. I see - fair enough. This was largely then a case of Guice not
releasing fast enough. Cool. I had misunderstood the extent.
I wanted to chat about what was missing from Guice that would have
allowed lifecycle as a pure extension for Sonatype's needs.
The only lifecycle code implemented in Sisu at the moment is the
Plexus lifecycle support in Sisu-Plexus, which is a pure extension
again built on top of the public Guice SPI.
Yeah - I was under the impression that sisu-plexus needed more
generalized api support in sisu-guice… but if that's just the
ProvisionListener, then that's fine.
Never mind then. We can get on with releasing 3.1. Thanks for the
patch pointers above.
Christian.
--
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.
