Re: CssResource interface conflict?

Cool, thanks for the test case, it makes it a lot easier. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com.

Re: CssResource interface conflict?

I believe I came across this as well (see issue 8251). I wasn't able to pinpoint the root cause as you did, but there's a test case attached to the issue that might be helpful. -- You received this message because you are subs

Re: CssResource interface conflict?

I found it ;) (some grey hair further) the bug is in the method: ClassRenamer.endVisit(CssSelector x, Context ctx), in this line: actualReplacements.put(method, obfuscatedClassName); Because of the reuse of the parent class HasOuterContainerStyle, the method variable is the same when

Re: CssResource interface conflict?

Thanks Thomas, I will gather some more info. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to th

Re: CssResource interface conflict?

On Wednesday, March 19, 2014 1:03:42 AM UTC+1, Ed wrote: > > Can anybody please confirm that this is a bug? (so I can report it as such) > If you can produce a small repro case (ideally a complete Maven project so it's easy to build and setup in an IDE), then I'd say go ahead and file a bug w

Re: CssResource interface conflict?

Can anybody please confirm that this is a bug? (so I can report it as such) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@

CssResource interface conflict?

I am using a lot of small interface to compose bigger ones, but using this with CssResources seem to result in problems, like if I am using the @Shared annotation, which I am not :( Below one of the use case that is giving me problems. The micro interface that is extended by CssResource interfac