I figured out why it's working in my case. I'm using the gwt bom.
com.google.gwt
gwt
2.8.0-SNAPSHOT
pom
import
On Friday, April 29, 2016 at 7:49:27 PM UTC+1, Colin Alworth wrote:
>
> Got it - so GWT is cons
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 e
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 group
I'm using the enforcer plugins with no complains.
org.apache.maven.plugins
maven-enforcer-plugin
1.4.1
enforcer
enforce
3.3.1
Should, and does if you have no enforcer. We needed the enforcer due to
arguing between far downstream dependencies from assorted other projects
that kept resulting in fun conflicts (in cases where there was no
guaranteed backward compat).
I'll make up a patch, thanks, I didn't know how hard and f
Why use 5.0.1 when there's 5.0.3 and ASM guarantees backwards compatibility?
FWIW, Maven should use 5.0.3 by default.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an e
It looks like a recent change is causing what is technically a version
conflict in GWT when used from maven. A project I work on uses the
maven-enforcer-plugin to avoid conflicts, and in a rebuild this morning we
ran into this error.
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce) @ gw
