Hi Stuart!

I'm currently debugging through a maven plugin hack I do atm. The underlying 
problem I had was not a guice problem but misinterpretation about what is 
available in the contexts. I wrongly assumed that all @Component injectable 
stuff of a Mojo is also available for injection inside other components (nested 
in a plugin mojo). But that is not the case because they get set without guice 
but 'manually' via the PluginParameterExpressionEvaluator afterwards.

LieGrue,
strub




----- Original Message -----
> From: Stuart McCulloch <[email protected]>
> To: Maven Developers List <[email protected]>
> Cc: 
> Sent: Friday, September 21, 2012 10:51 AM
> Subject: Re: how to best debug sisu-guice?
> 
> And if you can share more details about the problem you're debugging, you 
> might want to post them to the upstream guice list at 
> http://groups.google.com/group/google-guice in case it's already been fixed 
> in trunk.
> 
> --
> Cheers, Stuart
> 
> On 21 Sep 2012, at 08:41, Mark Struberg <[email protected]> wrote:
> 
>> 
>> 
>>  Hi!
>> 
>>  I need to debug through sisu-guice as I'm searching for a bug.
>> 
>>  Problem I face is that the source and binary of e.g. 
>> 
>> 
>>  com.google.inject.internal.MembersInjectorImpl<T>
>> 
>> 
>> 
>>  doesn't fit together (debugger hitting empty lines and is completely 
> off-method). 
>> 
>>  I already dropped the jars off my local maven repo and forced a reload 
> without luck.
>> 
>>  Where to get the _real_ sources from?
>> 
>> 
>>  txs and LieGrue,
>>  strub
>> 
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: [email protected]
>>  For additional commands, e-mail: [email protected]
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to