Thank Thomas for fixing this.
On Thu, Oct 2, 2014 at 3:26 PM, Thomas Broyer wrote:
>
>
> On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino
> wrote:
>>
>>
>>
>> On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors <
>> google-web-toolkit-contributors@googlegr
On Thursday, October 2, 2014 2:33:29 PM UTC+2, Manuel Carrasco Moñino wrote:
>
>
>
> On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> We kind of knew this sort of incompatibility would happen, but I still
>> thi
On Thu, Oct 2, 2014 at 12:28 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> We kind of knew this sort of incompatibility would happen, but I still
> think GWT should continue get out of the business of rebasing
> everything.
> We should even
We kind of knew this sort of incompatibility would happen, but I still
think GWT should continue get out of the business of rebasing
everything. We should even have a version of the JAR that can use
dynamic dependencies.
On Wed, Oct 1, 2014 at 3:16 PM, Manuel Carrasco Moñino
wrote:
> Thank Robe
Thank Roberto, that is the key, everything works if I exclude the asm
transitive dependency in my pom
org.eclipse.jetty
jetty-annotations
org.objectweb.asm
org.eclipse.jetty.orbit
This seems to be the error:
java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
org.objectweb.asm.MethodVisitor as super class
and the problem seems to be that you have ASM < 5 in your class path. (It
seems that MethodVisitor was an interface
Hi all,
Do anyone knows what could change lately which makes the compiler fail if
jetty annotations is in your classpath.
The way to reproduce is compiling any project which jetty-annotations.jar
before before gwt-dev.jar.
Attached trace.
--
You received this message because you are subscribe
