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,
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
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
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
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.
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
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
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
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
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
- 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
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
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
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
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
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
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
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
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
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
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
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
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
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 =
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
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:
- 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
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
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
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]
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
31 matches
Mail list logo
