You know you re both right. Funny thing is I had GIN 2.0 in my project a
long time but since I had not realised that gin was improved God knows how
many times I needlessly rebuilt my project. *facepalm*
On Thursday, February 28, 2013 11:43:57 PM UTC+1, Thomas Broyer wrote:
On Thursday,
Hello!
I just experimented somewhat with Gin and realized that it (v2.0) seems to
break the incremental compilation feature of GWT's development mode, ie.
where I just have to save the .java source file and the gwt dev mode server
automatically incorporates the changes.
Can someone confirm
I just experimented somewhat with Gin and realized that it (v2.0) seems to
break the incremental compilation feature of GWT's development mode, ie.
where I just have to save the .java source file and the gwt dev mode server
automatically incorporates the changes.
Not exactly sure what
On Thursday, February 28, 2013 6:43:11 PM UTC+1, Marc wrote:
Hello!
I just experimented somewhat with Gin and realized that it (v2.0) seems to
break the incremental compilation feature of GWT's development mode, ie.
where I just have to save the .java source file and the gwt dev mode
On Thursday, February 28, 2013 11:21:48 PM UTC+1, alucard wrote:
On Thursday, February 28, 2013 6:43:11 PM UTC+1, Marc wrote:
Hello!
I just experimented somewhat with Gin and realized that it (v2.0) seems
to break the incremental compilation feature of GWT's development mode, ie.
I believe you're right. If you mess with DI stuff (for example add a new
parameter to a constructor annotated with @Inject) the code will break when
you reload. You have to rebuild the project at that point. I believe this
is due to gin using generators which are not triggered on
