date:20141001

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

2014-10-01 Thread Julien Dramaix

I confirm, I just add GXT to one of my test project and I'm not able to use
sdm anymore:
[ERROR] Current binding properties are expanding to more than one
permutation but per-file compilation requires that each compile operate on
only one permutation.

On Wed, Oct 1, 2014 at 2:34 AM, Colin Alworth niloc...@gmail.com wrote:

The 'test runner' in this case is just the name of a regular module file,
which happens to be used for running lots of tests, most of which look like
EntryPoints. Nothing too magic going on here, and I've gotten this error by
running modules for more 'normal' gwt apps as well, typically when I stop
SDM, restart it, and then refresh the browser or click Compile without
first using the SDM off bookmarklet.

I'm not completely aware of your configuration but... it appears that
you're using incremental compiles from a test runner, and this test runner
isn't restricting the permutations to just 1. And that is being caught by
an assertion.

You can fix this by adding some set-property tags to your test .gwt.xml
files.

I hadn't thought of this use case, so I'm not sure if it's fair to tell
people to restrict their permutation or if we need to find a better way.
Thoughts?

Does this mean that we expect all projects to already be confined to one
permutation, either via set-property or collapse-all-permutations? Is there
no way to achieve that synthetically?

Further, does this mean that one cannot test in multiple browsers
simultaneously, for example re-compiling in FF until some behavior is
satisfactory, then moving to Chrome (at least without stopping and
restarting SDM)?

--
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/cdf99604-44c9-41b5-9cca-4f45227a3c89%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/cdf99604-44c9-41b5-9cca-4f45227a3c89%40googlegroups.com?utm_medium=emailutm_source=footer
.

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/CABb_3%3D6fovE52iouAswSHFpQ8dp1sLZYDTUmqBD--bhtvC0akg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop

2014-10-01 Thread Michael Vogt

Thank you for your answers. Yes this was the problem.


Cheers,
Michael

-- 
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/CAAfA4Fx7i_jMj66hfOruEtmfjeC0%3DJei-2XNazkuHsbLPHtKrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop

2014-10-01 Thread 'Chris DiGiano' via GWT Contributors

Have you enabled jsInterop mode via the compiler flag? It looks like this
on the command line:
 -XjsInteropMode JS

Chris

On Tue Sep 30 2014 at 7:05:23 AM Michael Vogt mich...@michaelvogt.eu
wrote:

 Btw, when calling parse() out of jsni or in the browser console, it works
 fine. So the Javascript side is ok.

 --
 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/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] BeanValidation java 8 upgrade

2014-10-01 Thread Fabien Dumay

Dear contributors,

This weekend, Thomas requested volunteers to make the bean validation 
compliant with java 8.
The Putnami team (Theophane and I) is interested to contribute on that 
issue. but we need a bit more inputs.

1. What is the due date?
2. Is the bean validation is only required for the Editor framework and 
RequestFactory or does GWT allow other entry point to the API?
3. What is the latitude we've got? Can we submit a patch to replace the 
hibernate-validation or is the task is just to upgrade to 4.3.2?
4. Is there any expectations to get bean validation 1.1 soon?

The only inputs that we have are:
the review : 9320 https://gwt-review.googlesource.com/#/c/9320/ and the 
issues 7661 
https://code.google.com/p/google-web-toolkit/issues/detail?id=7661 and 
8914 https://code.google.com/p/google-web-toolkit/issues/detail?id=8914
Is there more stuff, maybe requirements?

Regards.

--
Fabien
http://pwt.putnami.org

-- 
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/f6f812f3-dd2a-443b-8dc7-f4d4161c17c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: BeanValidation java 8 upgrade

2014-10-01 Thread Thomas Broyer

On Wednesday, October 1, 2014 11:39:44 AM UTC+2, Fabien Dumay wrote:

Dear contributors,

This weekend, Thomas requested volunteers to make the bean validation
compliant with java 8.
The Putnami team (Theophane and I) is interested to contribute on that
issue. but we need a bit more inputs.

1. What is the due date?

I'll let others chime in, but I think we'd want it ASAP.

2. Is the bean validation is only required for the Editor framework and
RequestFactory or does GWT allow other entry point to the API?

Editor and RF have a dependency on the ConstraintViolation interface
(mostly as consumers, but RF also implements it to map violations
received by the server to the Receiver's onConstraintViolations)

3. What is the latitude we've got? Can we submit a patch to replace the
hibernate-validation or is the task is just to upgrade to 4.3.2?

Nobody maintains Bean Validation support in GWT (on roadmap, nobody to
review patches, etc.), so I think everything's possible, provided you don't
break backwards compatibility.
The short-term goal is to have GWT compile with a JDK 8, anything else is
bonus, but shouldn't slow you down.
I'll advocate to split it into a separate project after 2.7 (or maybe for
2.7 if it takes too much time/energy to update it for JDK 8)

4. Is there any expectations to get bean validation 1.1 soon?

See #3 above.

The only inputs that we have are:
the review : 9320 https://gwt-review.googlesource.com/#/c/9320/ and the
issues 7661
https://code.google.com/p/google-web-toolkit/issues/detail?id=7661 and
8914 https://code.google.com/p/google-web-toolkit/issues/detail?id=8914
Is there more stuff, maybe requirements?

Have a look at commit logs, and possibly refer to their corresponding
review (there should be links in most commits; and when there's not and
there's a Change-Id, you can copy/paste it to Gerrit's search box)

--
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/5608f3f1-d1ff-4079-b3da-451ad0eaca23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Current DevMode -superDevMode issues for our setup

2014-10-01 Thread Jens

Hi,

I just tried latest trunk (without Daniels upcoming automatic recompile on 
page reload patch) and the following describes our current setup and the 
issues we have with DevMode -superDevMode.


*TL;DR:*
*- public resources are not copied to war output directory. Only 
app.nocache.js will be generated. We need public resources.*
*- the generated app.nocache.js of DevMode -superDevMode does not set all 
binding properties so SDM fails because more than 1 permutation has been 
detected. In our case GWT locale and one of our properties is not defined 
with a default value.*


We use GWTs public folder feature quite a bit and rely on the fact that 
DevMode copies the content of all public folders to the war output 
directory as soon as DevMode has started (without ever accessing the app 
through the browser).

With current state of DevMode -superDevMode it seems like that only an 
app.nocache.js file will be copied to the war output directory and no other 
public resources at all. That won't work for us because in our public 
folders we have an index.tpl file that will be used by a servlet to 
generate the GWT host page. There are also other files in our public 
folders that should be deployed on server like icon fonts and other stuff 
that is not managed by GWT ClientBundle resources.

I also noticed that the CodeServer now provides some public resources but 
it seems like it only provides files but not directories, for example 
public/robots.txt has been copied but public/fonts/* is missing. Not sure 
if that is intended behavior, maybe there is a bug in the resource copying 
code.

Now if I workaround the above issue by copying our public resources 
manually to the war output directory we still can't launch our app because 
the Recompiler (automatically started by the generated app.nocache.js file) 
detects multiple permutations and thus fails. The reason is that the 
generated app.nocache.js only defines the user.agent property and nothing 
more. Are we now required to change GWT module xml files to set default 
property values? 

So for us the only way to use SDM without issues is to not use DevMode 
-superDevMode and do it the ordinary compile once, then deploy, then use 
bookmarklets way.


-- J.






-- 
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/e4ac65c8-9f28-4128-89cd-9df5d4a5b43f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Current DevMode -superDevMode issues for our setup

2014-10-01 Thread Jens

Now I have applied Daniels patch to always recompile on reload. The
situation is now:

- Resources from public folders are still missing so I need to copy them
manually
- the generated app.nocache.js file of DevMode -superDevMode correctly sets
all permutation properties so the first compile works now
- recompiles on page reload work well

The only other thing I noticed is that the RemoteServiceServlet always uses
localhost to fetch GWT-RPC policy files. However we sometimes need to
access our app via IP (e.g. access local dev environment from IE browser in
a VM). If we do so, the code server must also run on that IP because the
new app.nocache.js file constructs the recompile URL based on the current
hostname of Window.Location. However that means we must override
RemoteServiceServlet.getCodeServerPolicyUrl(). While doing so I noticed
that the variable RemoteServiceServlet.codeServerPort is private. I think
we should make it protected or add a protected getter to access it so it
can be used in RemoteServiceServlet.getCodeServerPolicyUrl().

Alternatively we could introduce gwt.codeserver.ip system property instead
and fallback to localhost if it is not specified.

So I would propose the following changes:

- Make sure ALL public resources (files + directories) are copied to war
output directory once DevMode -superDevMode has been started
- instead of hard coding localhost in
RemoteServiceServlet.getCodeServerPolicyUrl() we should introduce
gwt.codeserver.ip system property and fallback to localhost if it is not
specified. Alternatively make codeServerPort accessible in sub classes of
RemoteServiceServlet. However I would prefer a new system property because
thats what I would have implemented anyway if I would need to override the
method.

-- J.

--
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/aa6d5a8b-4007-43f1-be34-fd3ba9937932%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop

2014-10-01 Thread 'John Stalcup' via GWT Contributors

Make sure turn turn on -XjsInteropMode JS

On Tue, Sep 30, 2014 at 9:18 AM, 'Chris DiGiano' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Have you enabled jsInterop mode via the compiler flag? It looks like this
on the command line:
-XjsInteropMode JS

Chris

On Tue Sep 30 2014 at 7:05:23 AM Michael Vogt mich...@michaelvogt.eu
wrote:

Btw, when calling parse() out of jsni or in the browser console, it works
fine. So the Javascript side is ok.

--
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/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com?utm_medium=emailutm_source=footer
.
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/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAFw3gJ_PjHJ0K89e%2B6Li1dL21TubXRoG%2B9aA-H4d5YWMcWjcEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: JsInterop

2014-10-01 Thread 'Daniel Kurka' via GWT Contributors

Make sure turn turn on -XjsInteropMode JS

-Daniel

On Wed, Oct 1, 2014 at 12:03 PM, 'John Stalcup' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Make sure turn turn on -XjsInteropMode JS

On Tue, Sep 30, 2014 at 9:18 AM, 'Chris DiGiano' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Have you enabled jsInterop mode via the compiler flag? It looks like this
on the command line:
-XjsInteropMode JS

Chris

On Tue Sep 30 2014 at 7:05:23 AM Michael Vogt mich...@michaelvogt.eu
wrote:

Btw, when calling parse() out of jsni or in the browser console, it
works fine. So the Javascript side is ok.

--
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/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com?utm_medium=emailutm_source=footer
.
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/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAFw3gJ_PjHJ0K89e%2B6Li1dL21TubXRoG%2B9aA-H4d5YWMcWjcEw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ_PjHJ0K89e%2B6Li1dL21TubXRoG%2B9aA-H4d5YWMcWjcEw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

--
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/CALLujipaFHw%2BL_%3D-zKZ5LXFp%3DKfPToxPzyuhT-92fRbseQiTow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7 release plan

2014-10-01 Thread 'Daniel Kurka' via GWT Contributors

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a beta1
build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for 1-2
weeks* for google internal feedback, if there is no serious issues we are
going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/
(dankurka)
- Sending the wrong permutation to the client in SDM, if no files have
changed (dankurka).
- Investigate why some people are seeing errors with incremental not
restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when using SDM
(skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage (goktug)
(promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

*If you have any outstanding patches that you thing need to go into GWT
2.7, please bring them to our attention, by replying to this thread or
adding me as a reviewer on Gerrit and setting the topic to GWT2.7.*

-Daniel

--
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/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 release plan

2014-10-01 Thread 'Brian Slesinsky' via GWT Contributors

- Make sure sample apps work with DevMode -superdevmode
- I think we're waiting on a patch to CLDR 25

On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues we
are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

2014-10-01 Thread 'John Stalcup' via GWT Contributors

We have a short list of issues that have to be addressed before 2.7 RC, and
this is on the list.

On Wed, Oct 1, 2014 at 1:13 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

I confirm, I just add GXT to one of my test project and I'm not able to
use sdm anymore:
[ERROR] Current binding properties are expanding to more than one
permutation but per-file compilation requires that each compile operate on
only one permutation.

On Wed, Oct 1, 2014 at 2:34 AM, Colin Alworth niloc...@gmail.com wrote:

You can fix this by adding some set-property tags to your test
.gwt.xml files.

I hadn't thought of this use case, so I'm not sure if it's fair to tell
people to restrict their permutation or if we need to find a better way.
Thoughts?

Does this mean that we expect all projects to already be confined to one
permutation, either via set-property or collapse-all-permutations? Is there
no way to achieve that synthetically?

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/CABb_3%3D6fovE52iouAswSHFpQ8dp1sLZYDTUmqBD--bhtvC0akg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6fovE52iouAswSHFpQ8dp1sLZYDTUmqBD--bhtvC0akg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAFw3gJ8iBDL7p9FObj2F0ax0N9bQ15iSdi2cY4_WOKOKyO%2BKSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 release plan

2014-10-01 Thread Julien Dramaix

Does that mean that GssResource will not be included in GWT 2.7 ?

I've planned to work on that Friday. Create patches in order to submit the
code in the gwt core but GSS needs Java 7 and you seem to say that GWT 2.7
has to support Java 6.

What is your plan with GSS ?

On Wed, Oct 1, 2014 at 9:23 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

- Make sure sample apps work with DevMode -superdevmode
- I think we're waiting on a patch to CLDR 25

On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CABb_3%3D7a4S4F8hrxNhSfjKTCxLRx299cwMvxtKGVssAHpRowqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 release plan

2014-10-01 Thread Manuel Carrasco Moñino

On Wed, Oct 1, 2014 at 9:23 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

- Make sure sample apps work with DevMode -superdevmode

I'm planing to do a exhaustive testing this week and verify that last
changes are reliable enough.

- I think we're waiting on a patch to CLDR 25

Patch is ready for review.

On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAtcBQUex7DxTWg64ZSgrLS_PWZnifC06gKbqk-G-ti%2BSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread Julien Dramaix

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

 Dear GWT lovers,

 I've just tried to compile several projects with the last snapshot of GWT
 2.7.0 using the PRETTY mode flag and several permutations. I noticed that
 only one js file (corresponding to one permutation) is emitted with non
 obfuscated javascript. The other files for each other permutation contains
 obfuscated javascript.

 I've tested with GWT 2.6.1 and everything works as expected: all the files
 contain only non-obfuscated javascript.

 Julien


-- 
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Compiler Faiure

2014-10-01 Thread Manuel Carrasco Moñino

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 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/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
com.vaadin.prototype.wc:v-demo:war:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-war-plugin is missing. @ line 207, column 21
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Using the builder 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
 with a thread count of 1
[INFO] 
[INFO] 
[INFO] Building Demo project 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ v-demo ---
[INFO] Deleting /Users/manolo/eclipse/luna/v-demo/target
[INFO] 
[INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ v-demo 
---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ v-demo ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/Users/manolo/eclipse/luna/v-demo/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ v-demo ---
[INFO] Compiling 3 source files to 
/Users/manolo/eclipse/luna/v-demo/target/v-demo-1.0-SNAPSHOT/WEB-INF/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
v-demo ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/Users/manolo/eclipse/luna/v-demo/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
v-demo ---
[INFO] Not compiling test sources
[INFO] 
[INFO] --- maven-surefire-plugin:2.8.1:test (default-test) @ v-demo ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- gwt-maven-plugin:2.7.0-SNAPSHOT:compile (default) @ v-demo ---
[INFO] auto discovered modules [com.vaadin.prototype.wc.gwt.Demo]
[INFO] Compiling module com.vaadin.prototype.wc.gwt.Demo
[INFO] [ERROR] Unexpected internal compiler error
[INFO] java.lang.IncompatibleClassChangeError: class 
com.google.gwt.dev.javac.asm.CollectMethodData has interface 
org.objectweb.asm.MethodVisitor as super class
[INFO]  at java.lang.ClassLoader.defineClass1(Native Method)
[INFO]  at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
[INFO]  at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[INFO]  at java.net.URLClassLoader.defineClass(URLClassLoader.java:455)
[INFO]  at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
[INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:367)
[INFO]  at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
[INFO]  at java.security.AccessController.doPrivileged(Native Method)
[INFO]  at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
[INFO]  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
[INFO]  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
[INFO]  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
[INFO]  at java.lang.Class.getDeclaredMethods0(Native Method)
[INFO]  at java.lang.Class.privateGetDeclaredMethods(Class.java:2688)
[INFO]  at java.lang.Class.getDeclaredMethod(Class.java:2115)
[INFO]  at 
java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1431)
[INFO]  at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:72)
[INFO]  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:494)
[INFO]  at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:468)
[INFO]  at java.security.AccessController.doPrivileged(Native Method)
[INFO]  at java.io.ObjectStreamClass.init(ObjectStreamClass.java:468)
[INFO]  at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:365)
[INFO]  at

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread 'Roberto Lublinerman' via GWT Contributors

Can you reproduce that from the command line in a regular compile? If so
can you post all the flags passed to the compiler?

On Wed, Oct 1, 2014 at 2:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of GWT
2.7.0 using the PRETTY mode flag and several permutations. I noticed that
only one js file (corresponding to one permutation) is emitted with non
obfuscated javascript. The other files for each other permutation contains
obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAC7T7gnRLixpdnwY8X-tsnRd4btdie20U_GCCx1i0p2s6KZ1CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread Manuel Carrasco Moñino

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Dear GWT lovers,

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAu9usDYZNNoC%3D5NN-_sTpEpS4B%2B%3DnayuNsQb2N6iGaTKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

2014-10-01 Thread 'Roberto Lublinerman' via GWT Contributors

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 in ASM 4 and is now an abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

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 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/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread Manuel Carrasco Moñino

Roberto, in my case this is the command line:

/Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/bin/java
-Xmx512m -classpath . . . -Dgwt.persistentunitcachedir= target
com.google.gwt.dev.Compiler -logLevel INFO -style PRETTY -war
target/v-demo-1.0-SNAPSHOT -localWorkers 8 -draftCompile -XnocheckCasts
-compileReport -XfragmentCount -1 -sourceLevel 1.7 -XjsInteropMode NONE
-extra target/extra -gen v-demo/target/.generated
com.vaadin.prototype.wc.gwt.Demo

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

2014-10-01 Thread Manuel Carrasco Moñino

Thank Roberto, that is the key, everything works if I exclude the asm
transitive dependency in my pom

dependency
groupIdorg.eclipse.jetty/groupId
artifactIdjetty-annotations/artifactId
exclusions
exclusion
artifactIdorg.objectweb.asm/artifactId
groupIdorg.eclipse.jetty.orbit/groupId
/exclusion
/exclusions

On Wed, Oct 1, 2014 at 11:46 PM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

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 in ASM 4 and is now an abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

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 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/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CAM28XAvmpneRqr1LLry_C612U7PsdY-raj9fPo_5ysAJ3qoGaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

2014-10-01 Thread 'Ray Cromwell' via GWT Contributors

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
man...@apache.org wrote:
Thank Roberto, that is the key, everything works if I exclude the asm
transitive dependency in my pom

On Wed, Oct 1, 2014 at 11:46 PM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

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 in ASM 4 and is now an abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

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 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/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.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/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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/CAPVRV7fUFGt8ksPPoPTwhxUN2xBjVLLoJ%2B%3DbooMpDoy6cN5wWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 release plan

2014-10-01 Thread 'Daniel Kurka' via GWT Contributors

To summarize the discussion I had with Julien over hangouts:

We are not going to require Java 7 for GWT 2.7 since we can not make GSS
default in GWT 2.7 (or we do have to postpone the release).
We will try to get GSS into GWT master and make it available as an
experimental feature in GWT 2.7 which will require Java 7 (if you use it).

On Wed, Oct 1, 2014 at 2:15 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Does that mean that GssResource will not be included in GWT 2.7 ?

I've planned to work on that Friday. Create patches in order to submit the
code in the gwt core but GSS needs Java 7 and you seem to say that GWT 2.7
has to support Java 6.

What is your plan with GSS ?

On Wed, Oct 1, 2014 at 9:23 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

- Make sure sample apps work with DevMode -superdevmode
- I think we're waiting on a patch to CLDR 25

On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on
the new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirrw0BL1yfX7nxLbH-yVLEofbQM%2BBn-ZtgmriuW56SMNQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.
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/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8y2fE4WQqFeXiJCVwTwD6XbdWiKrR3fH28qzMLvk0Uvg%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CABb_3%3D7a4S4F8hrxNhSfjKTCxLRx299cwMvxtKGVssAHpRowqA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7a4S4F8hrxNhSfjKTCxLRx299cwMvxtKGVssAHpRowqA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread Colin Alworth

I also can reproduce this - when style is set to PRETTY, 4 of the 17
permutations starts off with the PRETTY setup code (from the linker?), then
moves on to have all obfuscated (and sorted, etc) JS from the compilation
process:

var $wnd = $wnd || window.parent;
var __gwtModuleFunction = $wnd.explorer;
var $sendStats = __gwtModuleFunction.__sendStats;
$sendStats('moduleStartup', 'moduleEvalStart');
var $gwt_version = 2.7.0-SNAPSHOT;
var $strongName = '1C1FC666B8D8D4A5634A1EDA3B51C36D';
var $gwt = {};
var $doc = $wnd.document;
var $moduleName, $moduleBase;
function __gwtStartLoadingFragment(frag) {
var fragFile = 'deferredjs/' + $strongName + '/' + frag + '.cache.js';
return __gwtModuleFunction.__startLoadingFragment(fragFile);
}
function __gwtInstallCode(code) {return
__gwtModuleFunction.__installRunAsyncCode(code);}
function __gwt_isKnownPropertyValue(propName, propValue) {
return __gwtModuleFunction.__gwt_isKnownPropertyValue(propName, propValue);
}
function __gwt_getMetaProperty(name) {
return __gwtModuleFunction.__gwt_getMetaProperty(name);
}
var $stats = $wnd.__gwtStatsEvent ? function(a) {return
$wnd.__gwtStatsEvent(a);} : null;
var $sessionId = $wnd.__gwtStatsSessionId ? $wnd.__gwtStatsSessionId : null;
function Qg(){}
function lr(){}
function fu(){}
function nu(){}
function Cu(){}...

file names, sizes:
23908346   0D4B0A8AEFAF8328F37ABFBECEB765AC.cache.js
23900780   102B4372CC1E48D4E25EF20E66AD58DC.cache.js
23900946   10F8674F5E5DA2F77E606EDC3EF15643.cache.js
23900106   19BE3EA887194EC666A99E7BF57466C9.cache.js
3179517   1C1FC666B8D8D4A5634A1EDA3B51C36D.cache.js
23900433   467DE13BCB709965841DEF1F6BFD4785.cache.js
23917825   52AE506F1022BBF96CD25D74BD321C21.cache.js
23907954   6D952B9399698247258186190F8E0C38.cache.js
23900411   BB376480C0E3F616DF9CC28CCF948D0B.cache.js
23900195   C603EC38E0BF3A20A865927C32E7F122.cache.js
3143293   C868922D674E3536B6E83AF9DC005B4C.cache.js
23900252   CFB5CC0D39830766B7CCC22F07FBDD98.cache.js
3129165   D60063CBD8120FF39347C97C3C38B770.cache.js
3225082   DDCA4900448CB91C57415D5B87D0F4A8.cache.js
2397   E11B2F6059BED303323AE4942F78E157.cache.js
23910979   F8003A30DB63AC175E0F7C5D0DF1EEA5.cache.js
23900163   FD1978D213B1B1592E0DC19E4F7FC46B.cache.js

A quick read of the compilation-mappings doesn't show a lot in common as to
why this might be happening - D60063 is theme=neptune, user.agent=ie9 while
DDCA49 is theme=gray, user.agent=safari, 1C1FC is theme=gray,
user.agent=gecko1_8, and C86892 is theme=gray, user.agent=ie8.

Compiled from gwt-maven-plugin 2.7.0-SNAPSHOT as well.

On Wed, Oct 1, 2014 at 4:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

 Roberto, in my case this is the command line:

 /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/bin/java
 -Xmx512m -classpath . . .  -Dgwt.persistentunitcachedir= target
 com.google.gwt.dev.Compiler -logLevel INFO -style PRETTY -war
 target/v-demo-1.0-SNAPSHOT -localWorkers 8 -draftCompile -XnocheckCasts
 -compileReport -XfragmentCount -1 -sourceLevel 1.7 -XjsInteropMode NONE
 -extra target/extra -gen v-demo/target/.generated
 com.vaadin.prototype.wc.gwt.Demo

 I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.





 On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino man...@apache.org
  wrote:

 I could verify the issue.
 A clue, It seems that the last emitted permutation is the only one
 un-obfuscated.

 As a workaround you can collapse-all-properties, and the result is PRETTY

 - Manolo

 On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
  wrote:

 Am I the only one to have this problem ?

 On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

 Dear GWT lovers,

 I've just tried to compile several projects with the last snapshot of
 GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
 that only one js file (corresponding to one permutation) is emitted with
 non obfuscated javascript. The other files for each other permutation
 contains obfuscated javascript.

 I've tested with GWT 2.6.1 and everything works as expected: all the
 files contain only non-obfuscated javascript.

 Julien


  --
 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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 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

Re: [gwt-contrib] Re: Change the superDevMode to be the default for dev-mode?

2014-10-01 Thread Brandon Donnelson

Just an update. I've contacted Jetbrains dev to add a flag to turn on
DevMode with -nosuperDevMode and I'm finishing up the changes with GPE
switches.

On Tuesday, September 30, 2014 4:59:28 PM UTC-7, John Stalcup wrote:

Brandon and I talked a bit about if offline and just the summarize:

If we want to accomplish making SuperDevMode on as the default behavior
in the DevMode launcher in GPE it is going to require some changes in
Brandon's work regardless of whether we do it via updating the default
value of the flag in GWT (because he'll need to start adding
-nosuperDevMode when Classic DevMode is selected) or instead update the
default setting of the radio button in the GPE launcher.

So since it's the same amount of work either way, and since updating the
default value of the flag in GWT has the advantage of having an effect for
command line users as well, this option is preferable.

On Tue, Sep 30, 2014 at 4:31 PM, Brandon Donnelson branfl...@gmail.com
javascript: wrote:

Gotcha. Well, I baked in -superDevMode program arg switch, and this is
also backported in an embedded jar. I would have to take into account some
switch to turn back on DevMode. I was hoping to alleviate the pain of
changing the program args by hand.

On Tuesday, September 30, 2014 4:28:18 PM UTC-7, John Stalcup wrote:

Goktug mentioned that he thinks the option should be on be default in
GWT, which would mean no change necessary in GPE. And I agree.

On Tue, Sep 30, 2014 at 4:21 PM, Brandon Donnelson branfl...@gmail.com
wrote:

Should I make this default behavior in GPE? On by default?

On Tuesday, September 30, 2014 3:40:15 PM UTC-7, Thomas Broyer wrote:

Fwiw, we made it the default in the gwt-maven-plugin.

--
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+unsubscribe@
googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-web-toolkit-contributors/bf5eda80-7c71-
4daa-9e84-98521c108b69%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/bf5eda80-7c71-4daa-9e84-98521c108b69%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

https://groups.google.com/d/msgid/google-web-toolkit-contributors/cf5783b0-a94a-48b4-a92c-15c85e318e18%40googlegroups.com?utm_medium=emailutm_source=footer
.

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/a41dc100-ecdf-48cd-a8d2-d92a5f098eef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread 'Roberto Lublinerman' via GWT Contributors

I'll look into it.

Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?

On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Roberto, in my case this is the command line:

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 release plan

2014-10-01 Thread Cristian Rinaldi

- JsInterop Preview is part of the release?

El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues we
are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 release plan

2014-10-01 Thread 'Brian Slesinsky' via GWT Contributors

It's experimental and hidden behind a flag, but it's there.

On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com
wrote:

- JsInterop Preview is part of the release?

El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:

Hi all,

we just settled on a GWT 2.7 release plan:

- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we put out a
beta1 build, this should be no later than *October 7th.*
- Putting out a *beta1 externally* allows us to collect feedback on the
new super dev mode integration externally as well.
- We are going to *flip incremental to default* tomorrow and *wait for
1-2 weeks* for google internal feedback, if there is no serious issues
we are going to *put out RC1*
- GWT 2.7 will still be compatible with Java 6.

Patches / Fixes that need to go in:
- Recompile on reload: https://gwt-review.googlesource.com/#/c/9323/ (
dankurka)
- Sending the wrong permutation to the client in SDM, if no files have
changed (dankurka).
- Investigate why some people are seeing errors with incremental not
restricting to one permutation (dankurka).
- Public directories are not copied o the war directory when using SDM
(skybrian).
- Restore Java 6 compatibility (skybrian).
- Document limitations of JsonUtils.safeEval and discourage usage
(goktug) (promote Json.parse)

Patches that are nice to have:
- Improve exception logging in SDM (goktug).

-Daniel

--
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/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d5a4369-e03d-47ba-b8dd-5031e5460751%40googlegroups.com?utm_medium=emailutm_source=footer
.

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/CA%2B%2BRBT-M5mAXmj5Ox8iQihjzFFinLM%2Bc57tmdD1JGwEMxKJHAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread 'Roberto Lublinerman' via GWT Contributors

Fixed. Review at https://gwt-review.googlesource.com/#/c/9432.

The issue is only present with -localWorkers 1 and all workers except the
first would get incorrect options.

On Wed, Oct 1, 2014 at 4:23 PM, Roberto Lublinerman rlu...@google.com
wrote:

I'll look into it.

Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?

On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Roberto, in my case this is the command line:

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino
man...@apache.org wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAC7T7gmQcsR885h4CEtRvjCOfCnKi3jFvnJsDmzODo25J7Exqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule

2014-10-01 Thread Colin Alworth

It looks like changes to a few rebind rules are generating some new logspam 
when any GWT app compiles. Specifically, I'm seeing FocusImpl and 
LayoutImpl, though its possible there are others I haven't seen yet. From 
the dynatable example we can see the FocusImpl spam:
gwtc:
 [java] Compiling module com.google.gwt.sample.dynatable.DynaTable
 [java]Computing all possible rebind results for 
'com.google.gwt.user.client.ui.impl.FocusImpl'
 [java]   Rebinding com.google.gwt.user.client.ui.impl.FocusImpl
* [java]  Could not find an exact match rule. Using 'closest' 
rule replace-with 
class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/ based on fall 
back values. You may need to implement a specific binding in case the fall 
back behavior does not replace the missing binding*
 [java]Compiling 5 permutations
 [java]   Compiling permutation 0...
 [java]   Process output
 [java]  Compiling
 [java] Compiling permutation 1...
 [java]   Compiling permutation 2...
 [java]   Compiling permutation 3...


First, the rules themselves:
  !-- Firefox uses a hidden input to set accesskeys --
  replace-with 
class=com.google.gwt.user.client.ui.impl.FocusImplStandard
when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/
when-property-is name=user.agent value=gecko1_8/
  /replace-with

  !-- Safari uses a hidden input to set accesskeys and --
  !-- fires focus/blur after a timeout --
  replace-with class=com.google.gwt.user.client.ui.impl.FocusImplSafari
when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/
when-property-is name=user.agent value=safari/
  /replace-with

  !-- IE's implementation traps exceptions on invalid setFocus() --
  replace-with class=com.google.gwt.user.client.ui.impl.FocusImplIE6
when-type-is class=com.google.gwt.user.client.ui.impl.FocusImpl/
all
  any
when-property-is name=user.agent value=ie6/
when-property-is name=user.agent value=ie8/
  /any
  none
when-property-is name=user.agent value=ie9/
  /none
/all
  /replace-with

No express binding of FocusImpl to itself, or to Standard (interestingly 
Standard really seems to mean Gecko, at least according to that comment, 
calling out a FF specific issue). I can't comment much on that just yet, 
though I might make a suggestion later. 

This code is as a result of https://gwt-review.googlesource.com/#/c/5055/ 
(or 
https://gwt.googlesource.com/gwt/+/040b3e4392186e48689a6fc1f19cdf294f2b5651 
if you like), ostensibly to make IE9+ use FocusImpl instead of FocusImplIE6 
(or Standard, for example).

[java]Computing all possible rebind results for 
'com.google.gwt.user.client.ui.impl.FocusImpl'

...

[java]  Found better fallback match for replace-with 
class='com.google.gwt.user.client.ui.impl.FormPanelImpl'/
[java]  Checking rule replace-with 
class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/
[java] Checking if all subconditions are true (all)
[java]when-type-is 
class='com.google.gwt.user.client.ui.impl.FocusImpl'/
[java]   Yes, the requested type was an exact match
[java]Checking if all subconditions are true (all)
[java]   Checking if any subcondition is true (any)
[java]  when-property-is name='user.agent' 
value='ie8'/
[java] Property value is '*ie9*'
[java] Property value 'ie8' is the fallback of 
'[[ie9]]'
[java] No, the value did not match
[java]  No: All subconditions were false
[java]   No: One or more subconditions was false
[java]No: One or more subconditions was false
[java]  Rule did not match
[java]  Found better fallback match for replace-with 
class='com.google.gwt.user.client.ui.impl.FocusImplIE6'/
[java]  Checking rule replace-with 
class='com.google.gwt.user.client.ui.impl.FocusImplSafari'/
[java] Checking if all subconditions are true (all)
[java]when-type-is 
class='com.google.gwt.user.client.ui.impl.FocusImpl'/
[java]   Yes, the requested type was an exact match
[java]when-property-is name='user.agent' value='safari'/
[java]   Property value is 'ie9'
[java]   No, the value did not match
[java]No: One or more subconditions was false
[java]  Rule did not match
[java]  Checking rule replace-with 
class='com.google.gwt.user.client.ui.impl.FocusImplStandard'/
[java] Checking if all subconditions are true (all)
[java]when-type-is 
class='com.google.gwt.user.client.ui.impl.FocusImpl'/
[java]   Yes, the requested type was an exact match
[java]when-property-is name='user.agent'

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

2014-10-01 Thread Manuel Carrasco Moñino

On Thu, Oct 2, 2014 at 1:23 AM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:

I'll look into it.

Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?

There is a hidden task in our server which is only accessible for
authenticated users, I use it for manually building gwt against an specific
commit. I launched this built to check that the broken test was fixed with
John's commit https://gwt-review.googlesource.com/#/c/9400/ . Jenkins show
it to indicate that a worker is busy.

On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

Roberto, in my case this is the command line:

I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.

On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino
man...@apache.org wrote:

I could verify the issue.
A clue, It seems that the last emitted permutation is the only one
un-obfuscated.

As a workaround you can collapse-all-properties, and the result is PRETTY

- Manolo

On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Am I the only one to have this problem ?

On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix
julien.dram...@gmail.com wrote:

Dear GWT lovers,

I've just tried to compile several projects with the last snapshot of
GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
that only one js file (corresponding to one permutation) is emitted with
non obfuscated javascript. The other files for each other permutation
contains obfuscated javascript.

I've tested with GWT 2.6.1 and everything works as expected: all the
files contain only non-obfuscated javascript.

Julien

--
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/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

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/CAM28XAuqJqy8B2ndD6wh0n%3DX7VWARnLyFWa2Cgsvx7w46GDCqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

Re: [gwt-contrib] Re: JsInterop

Re: [gwt-contrib] Re: JsInterop

[gwt-contrib] BeanValidation java 8 upgrade

[gwt-contrib] Re: BeanValidation java 8 upgrade

[gwt-contrib] Current DevMode -superDevMode issues for our setup

[gwt-contrib] Re: Current DevMode -superDevMode issues for our setup

Re: [gwt-contrib] Re: JsInterop

Re: [gwt-contrib] Re: JsInterop

[gwt-contrib] GWT 2.7 release plan

Re: [gwt-contrib] GWT 2.7 release plan

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

Re: [gwt-contrib] GWT 2.7 release plan

Re: [gwt-contrib] GWT 2.7 release plan

[gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

[gwt-contrib] Compiler Faiure

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

Re: [gwt-contrib] Compiler Faiure

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

Re: [gwt-contrib] Compiler Faiure

Re: [gwt-contrib] Compiler Faiure

Re: [gwt-contrib] GWT 2.7 release plan

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

Re: [gwt-contrib] Re: Change the superDevMode to be the default for dev-mode?

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

[gwt-contrib] Re: GWT 2.7 release plan

Re: [gwt-contrib] Re: GWT 2.7 release plan

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

[gwt-contrib] Spam logs: Could not find an exact match rule. Using 'closest' rule

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

31 matches

Site Navigation

Mail list logo

Footer information