what are the sisu (guice, cglib) artifacts?

[Wujek Srujek]

Hi. I am evaluating Guice for my new project again, and I noticed that there are some sisu artifacts. Even the mmain maven repository has a guice 3 pom.xml with a reference to some sisu-cglib artifact (with a note that it should be replaced when official cglib comes out, which probably has happened already?). Could anybody shed some light on this?

wujek

[Stuart McCulloch]

On 3 Aug 2012, at 16:32, Wujek Srujek wrote:

> Hi. I am evaluating Guice for my new project again, and I noticed that there are some sisu artifacts. Even the mmain maven repository has a guice 3 pom.xml with a reference to some sisu-cglib artifact (with a note that it should be replaced when official cglib comes out, which probably has happened already?). Could anybody shed some light on this?

See https://groups.google.com/forum/?fromgroups#!topic/google-guice/Rxk7d3SWFYE for the full history

Summary: it is a dependency of the build process, but is not required by Guice at runtime because it is embedded (and relocated) inside

If you look at the trunk build you will see that it now uses the latest official CGLIB dependency that includes the fix needed by Guice

> wujek

[Stuart McCulloch]

See also https://groups.google.com/forum/?fromgroups#!topic/google-guice/Wz1XrRuX69U which talks a bit more about sisu-guice

So sisu-cglib was a temporary build-time-only artifact needed to get Guice 3.0 out the door (it isn't in trunk and it won't be in the next release) and sisu-guice is just an unofficial/experimental branch of Guice

Neither artifact is actually needed to use Guice at compile or runtime with your application

[Wujek Srujek]

Thank you, I will definitely read the documents. When do you plan to release another version of Guice? Will it be 3.1 or 4? Is there a document that shows which new features will make it to that version? Will you maybe support lifecycle? (Like @PostConstruct, @PreDestroy, and ideally, also DSL-like configuration). I am asking as maybe we could wait a little / use your trunk for our app. How stable is the code in your repositories?

wujek

--
You received this message because you are subscribed to the Google Groups "google-guice" group.
To post to this group, send email to google...@googlegroups.com.
To unsubscribe from this group, send email to google-guice...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.

[Stuart McCulloch]

On 3 Aug 2012, at 16:56, Wujek Srujek wrote:

Thank you, I will definitely read the documents. When do you plan to release another version of Guice? Will it be 3.1 or 4?

There's plenty of demand for a new release, which will probably be 4.0, but I haven't heard when this will be...

Is there a document that shows which new features will make it to that version?

Not yet, but we'll probably create a page on the wiki (such as http://code.google.com/p/google-guice/wiki/Guice30) to list the new features and the API differences

Will you maybe support lifecycle? (Like @PostConstruct, @PreDestroy,

Unlikely to be in core - but there are extensions that support this by using the core SPI:

   http://code.google.com/p/tadedon/

   http://code.google.com/p/guiceyfruit/

I'm also looking at writing a flexible lifecycle extension using the new ProvisionListener SPI

and ideally, also DSL-like configuration).

Again this would be more of an extension rather than core feature, for example:

   https://github.com/svenefftinge/Guice-Modules-DSL

I am asking as maybe we could wait a little / use your trunk for our app. How stable is the code in your repositories?

Speaking personally trunk is stable - over at sisu-guice we regularly do releases based on Guice trunk (plus our local patches) and use them in production.

--

Cheers, Stuart