I'll see what I can do.
On Apr 1, 2013 6:56 AM, "Stuart McCulloch" <[email protected]> wrote:

> Ditto, happy to help where necessary.
>
> Sam - any chance you could put a zip with your internal changes somewhere
> so that people can give them a spin while the git-sync is fixed?
>
> --
> Cheers, Stuart
>
> On 1 Apr 2013, at 06:24, Tim Boudreau <[email protected]> wrote:
>
> Ping?
>
> The offer of assistance stands...
>
> -Tim
>
> On Sunday, March 10, 2013 6:34:35 PM UTC-4, Sam Berlin wrote:
>>
>> There's a few minor changes we wanna put into trunk, and then I think we
>> can put a 3.1.0 RC out pretty easily.  Sorry for the troubles. :-/
>>
>> The changes are basically:
>>
>>    * Add some explicit @Inject constructors in the servlet extension (to
>> play better with requireAtInjectOnConstructors)
>>    * Add a ScopingException subclass, thrown by the ServletScopes
>> checkState calls, to better identify failures.
>>    * Update Guice to a new CGLIB that uses ASM4.
>>    * Update ProvisionListener so it works with toInstance & bindConstant
>> bindings.
>>    * Fix ContinuingServletHttpRequest to allow getCookies() to return null
>>    * Change AssistedInject so it fails if it tries to construct a class
>> that has a scoping annotation (instead of ignoring the scope).
>>
>> ... there's just some issues with our sync process that's delaying
>> pushing them out.  Once they're in git, I don't see any reason to delay an
>> RC.  (We might have to fix-up the poms, particularly for the cglib change.)
>>
>>  sam
>>
>>
>> On Sun, Mar 10, 2013 at 5:22 PM, Tim Boudreau <[email protected]> wrote:
>>
>>> I have a number of mini-frameworks that sit on top of Guice, and one of
>>> them uses features only available in the Guice trunk.  I am really tired of
>>> explaining to people why they need to use an unreleased trunk build of
>>> Guice in production code, and have had to repeatedly set up continuous
>>> builds of Guice on my and my customers' continuous integration servers.
>>>
>>> If the trunk is so fabulously stable that no changes have been necessary
>>> for an age, why not do a 3.1.0 release and get off the pot?
>>>
>>> I don't want to just gripe about it - if there's any way I can
>>> contribute to making that happen (resources, time, code, whatever), I will
>>> - just ask.
>>>
>>> -Tim
>>>
>>>  --
>>> 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 google-guice...@**googlegroups.com.
>>> To post to this group, send email to [email protected].
>>> Visit this group at 
>>> http://groups.google.com/**group/google-guice?hl=en<http://groups.google.com/group/google-guice?hl=en>
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>>
>>>
>>
>>  --
> 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.
>
>
>
>  --
> 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.
>
>
>

-- 
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.


Reply via email to