Re: [gwt-contrib] Maven conflict between gwt-dev's and jetty-annotations's asm-commons

2016-04-29 Thread Colin Alworth
Got it - so GWT is consistent, but the jetty vers we use talks about a different one, and our ant process should ignore what jetty asks for in favor of our copy. Filipe, here's the case, in a super-minimal pom, which will fail outright without any sources, just a dependency on gwt-dev and the

Re: [gwt-contrib] Re: Elemental 2 and J2CL timeline

2016-04-29 Thread Paul Stockley
I think once 2.8 is out the door we should definitely pursue setting up some projects to tackle the things that won't be in J2CL. This will really help a lot to alleviate many peoples fears, especially those with large projects that use Widgets, UiBinder etc. There has been a lot of vague

Re: [gwt-contrib] Maven conflict between gwt-dev's and jetty-annotations's asm-commons

2016-04-29 Thread Thomas Broyer
On Thursday, April 28, 2016 at 11:47:48 PM UTC+2, Colin Alworth wrote: > > I didn't know how hard and fast we could rely on ASM's backward compat > being. > This is true since ASM 4.0 (released in 2011): http://download.forge.objectweb.org/asm/asm4-guide.pdf Fortunately, they changed the

Re: [gwt-contrib] Maven conflict between gwt-dev's and jetty-annotations's asm-commons

2016-04-29 Thread Filipe Sousa
I'm using the enforcer plugins with no complains. org.apache.maven.plugins maven-enforcer-plugin 1.4.1 enforcer enforce 3.3.1