|Gin 2.0||Aragos||9/1/12 11:24 AM|
it's finally here: Gin's newest release, 2.0! You can download it now from Gin's download page.
The major version jump is due to the significant project changes since the last release. A lot of the internals have been completely rewritten, paving the way for a lot of new features. Some highlights of this release:
- Private Modules
- Automatic Refresh in DevMode
- Access to Package Private Types
These, as well as many bug fixes and other improvements couldn't have been completed without the help of many supporters and contributors: Thank you!
Note that this release is not compatible with GWT before version 2.4.0.
PS: I have to re-learn how to push this release to Maven but hopefully I can figure it out over the weekend. :)
|Re: Gin 2.0||Andrés Testi||9/1/12 5:52 PM|
Thanks a lot!
|Re: Gin 2.0||Cristian Rinaldi||9/1/12 6:05 PM|
Thanks for the improvements!
|Re: [google-gin] Re: Gin 2.0||juan_pablo_gardella||9/1/12 11:14 PM|
Where is the release notes?
2012/9/1 Cristian Rinaldi <csri...@gmail.com>
|Re: Gin 2.0||Evgeniy Bulanov||9/5/12 4:30 AM|
Good job, thanks.
P.S.: We are waiting the release in maven repo ;)
воскресенье, 2 сентября 2012 г., 1:24:25 UTC+7 пользователь Aragos написал:
|Re: Gin 2.0||Filipe Sousa||9/5/12 8:37 AM|
|Re: [google-gin] Re: Gin 2.0||Aragos||9/8/12 12:23 PM|
I prepared the maven release on staging, please test it and let me know if all is in order. Once I've gotten a bit of feedback I'll release it: https://oss.sonatype.org/content/repositories/comgooglegwtinject-268/com/google/gwt/inject/gin/2.0.0/
|Re: [google-gin] Re: Gin 2.0||Thomas Broyer||9/9/12 4:13 AM|
I don't know if you consider this too late to fix in 2.0 (as this hasn't been reported earlier) but I don't understand why GIN depends on gwt-servlet (I separate my client and server-side code in distinct modules, so my client module doesn't depend on gwt-servlet, and thus I have a transitive dependency on it with a different version than the one I use otherwise), and I wonder if guice-assistedinject could be changed to <optional>true</optional> (with 1.5, if I didn't use AssistedInject but added an explicit dependency on Guice 3.0, I'd have a transitive dependency on the 3.0-rc2; with 2.0 the dependency has been updated to Guice 3.0, but Guice is about to release a 3.1; in the end, I had to add AssistedInject to my project so I didn't investigate if excluding guice-assistedinject would have caused problems)
(I haven't yet tried 2.0, just looked at the POM out of curiosity)
|Re: [google-gin] Re: Gin 2.0||Abraham Lin||9/10/12 7:05 AM|
On Sunday, September 9, 2012 7:13:19 AM UTC-4, Thomas Broyer wrote:
I have no strong opinions about this, but does the transitive dependency really matter? If you declare a newer version of Guice in your POM, the transitive dependency is ignored, which seems to yield the desired outcome. And if you're not referencing AssistedInject classes, they (presumably) won't be loaded, and so any API incompatibilities at compile time should be avoided.
That being said, I'm not sure that using a newer version of Guice in a client project really makes sense (don't you generally need the Gin support as well?).
|Re: [google-gin] Re: Gin 2.0||Thomas Broyer||9/10/12 9:56 AM|
Well, it's mostly so that I use the same version of Guice everywhere in my app (client-side, server-side, standalone tools, etc.) and define that version once in the parent POM.
|Re: [google-gin] Re: Gin 2.0||Aragos||9/16/12 2:28 PM|
I was trying to remove the dependency on gwt-servlet (which admittedly doesn't make sense) and in doing so I deleted the existing staging version of the release. Unfortunately I seem to be unable to upload a new version at the moment - updates here when I have them.
As for making assisted inject optional, I don't think that'll work although I haven't tried it - but Gin uses assisted inject internally itself.
|Re: [google-gin] Re: Gin 2.0||Aragos||9/24/12 12:11 PM|
Ok, problems with Sonatype were fixed, the new maven release candidate is here: https://oss.sonatype.org/content/repositories/comgoogle-126/com/google/gwt/inject/gin/2.0.0/
Please test and let me know if it works. Once I have positive feedback I'll finalize the release.
|Re: [google-gin] Re: Gin 2.0||Filipe Sousa||9/25/12 2:07 AM|
I'm using ivy and it seems to work.
|Re: [google-gin] Re: Gin 2.0||Abraham Lin||9/27/12 11:51 AM|
Seems to work for me as well (using Maven).
|Re: [google-gin] Re: Gin 2.0||Aragos||9/27/12 12:10 PM|
Thanks for the feedback, the Maven release has been finalized. Enjoy! :)
On Thu, Sep 27, 2012 at 2:51 PM, Abraham Lin <atomknig...@gmail.com> wrote:
Seems to work for me as well (using Maven).
|Re: Gin 2.0||Chris Lercher||10/11/12 2:53 PM|
|Re: [google-gin] Re: Gin 2.0||Aragos||10/11/12 5:43 PM|
I've updated the compatibility page with Gin 2.0 features.
--To view this discussion on the web visit https://groups.google.com/d/msg/google-gin/-/A-U1ggIh3rEJ.
|Re: [google-gin] Re: Gin 2.0||Chris Lercher||10/13/12 9:27 AM|
On Friday, October 12, 2012 2:43:12 AM UTC+2, Aragos wrote:I've updated the compatibility page with Gin 2.0 features.
Thanks, that was quick. Are any points on the page planned for the next release?
|Re: [google-gin] Re: Gin 2.0||Aragos||10/13/12 10:02 AM|
Work on Gin is pretty slow right now (partially due to me being very busy elsewhere) so there are no concrete plans for the next release yet. Potential candidates are multibinding and more optimizations but that's very speculative.
|Re: [google-gin] Re: Gin 2.0||David Nouls||3/20/13 12:34 PM|
Any chance of getting support for custom scoping ? Or is that now available in 2.0 ?
Right now my code depends on the fact that GWT.create gives me a new scope,
but I could use an application wide scope as well and that is currently a bit cumbersome to support.
|Re: [google-gin] Re: Gin 2.0||Aragos||3/20/13 9:36 PM|
no one is working on custom scoping right now and I know of no plans to support it. Note that I don't think it will solve the issue you seem to have - separate Ginjectors will never share state, even if scoping were available.
To unsubscribe from this group and stop receiving emails from it, send an email to google-gin+...@googlegroups.com.