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

2016-04-28 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


1.8







[INFO] 

[INFO] Building gwt-java8 0.1.0-SNAPSHOT
[INFO] 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (default-cli) @ gwt-java8 ---
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 


[INFO] --- maven-enforcer-plugin:1.4.1:display-info (default-cli) @ 
gwt-java8 ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_92 normalized as: 1.8.0-92
[INFO] OS Info: Arch: x86_64 Family: mac Name: mac os x Version: 10.11.5


On Thursday, April 28, 2016 at 10:47:48 PM UTC+1, Colin Alworth wrote:
>
> 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 fast we could 
> rely on ASM's backward compat being. Probably should also put this in tools 
> so that we are consistent, and update the ant files so that we don't get 
> slightly different classes in maven vs zip archive...
>
> On Thu, Apr 28, 2016 at 3:59 PM Thomas Broyer  > wrote:
>
>> 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 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/900dbd13-941a-44f2-8497-e1d96fd74a65%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/b0404c71-5c11-44ca-a5b5-1afae6862922%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread Colin Alworth
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 fast we could rely
on ASM's backward compat being. Probably should also put this in tools so
that we are consistent, and update the ant files so that we don't get
slightly different classes in maven vs zip archive...

On Thu, Apr 28, 2016 at 3:59 PM Thomas Broyer  wrote:

> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/900dbd13-941a-44f2-8497-e1d96fd74a65%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CADcXZMzaWsJ209wWap4MDizws6r_ryVTJo_OMpWTs8kUms1woA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread Thomas Broyer
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/900dbd13-941a-44f2-8497-e1d96fd74a65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread Colin Alworth
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) @ gwt-project ---
[WARNING] 
Dependency convergence error for org.ow2.asm:asm-commons:5.0.3 paths to 
dependency are:
+-colins.super.duper:gwt-project:0.0.1-SNAPSHOT
  +-com.google.gwt:gwt-dev:2.8.0-SNAPSHOT
+-org.ow2.asm:asm-commons:*5.0.3*
and
+-colins.super.duper:gwt-project:0.0.1-SNAPSHOT
  +-com.google.gwt:gwt-dev:2.8.0-SNAPSHOT
+-org.eclipse.jetty:jetty-annotations:9.2.14.v20151106
  +-org.ow2.asm:asm-commons:*5.0.1*


This appears to have been introduced 
in https://gwt-review.googlesource.com/#/c/14461/, though it could have 
been earlier. I'm not familiar with how exactly we settled on 5.0.1, and if 
we must use that (and override jetty...), or if we can upgrade to 5.0.3 and 
not risk affecting jetty.

Locally, I'm overriding this by excluding asm-commons from my gwt-dev 
dependencies, and requiring 5.0.3, which seems to be working (minus a 
jsinterop issue, which I am now hunting...). Thoughts on which version we 
should require? I can make the patch once I have feedback.

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/6a916e9c-6757-4d18-9db3-f100bc1aa206%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread Thomas Broyer
Sorry, I didn't mean to keep a big "monolithic" project like we have now 
(I'm +1000 on modularization!), it can very well be a new "project", built 
separately, released at a different pace, etc.
My point was that it could be kept under the "GWT Project" umbrella, rather 
than a "third party" project. It can also be incubated as a third-party 
*now*, as we don't yet really know what GWT 3 will be, and then brought 
under the GWT Project umbrella when we know what GWT 3 will and won't be.
For such things like widgets and UiBinder, I think the "GWT Project" should 
provide a migration path from GWT 2 to GWT 3.

On Thursday, April 28, 2016 at 9:36:34 AM UTC+2, Goktug Gokdogan wrote:
>
> I think creating a new project is a good opportunity to start bundling 
> things out of GWT-SDK as agreed on in the initial roadmap.
>
> On Thu, Apr 28, 2016 at 12:27 AM, Thomas Broyer  
> wrote:
>
>> No need to create a new project; that can live in GWT proper BUT will 
>> only be supported by community members (i.e. not Google)
>>
>> --
>> 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 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad848b18-5451-4b7f-9c8f-bb58b86a9b81%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/09651ecc-76dd-4ee3-89b2-e8909419c69c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread 'Goktug Gokdogan' via GWT Contributors
I think creating a new project is a good opportunity to start bundling
things out of GWT-SDK as agreed on in the initial roadmap.

On Thu, Apr 28, 2016 at 12:27 AM, Thomas Broyer  wrote:

> No need to create a new project; that can live in GWT proper BUT will only
> be supported by community members (i.e. not Google)
>
> --
> 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
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad848b18-5451-4b7f-9c8f-bb58b86a9b81%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3tfVp53oa36DUqJTed5qFzKGujq%3DRdWkJNEiSGKYmD7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


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

2016-04-28 Thread Thomas Broyer
No need to create a new project; that can live in GWT proper BUT will only be 
supported by community members (i.e. not Google)

-- 
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 email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad848b18-5451-4b7f-9c8f-bb58b86a9b81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.