date:20160804

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-04 Thread Mark Duesbury

Problem solved.. 

I had the configuration in the wrong place. Should be...





  prepare-package



compile









-Xms2g -Xmx4g -Xss1024k

desktop.html

${project.build.directory}/${project.build.finalName}

true

true

true

INFO




It seems 2.8 is less forgiving than 2.7 in this regard




>>

-- 
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/cb0ee9c1-8d2e-44e0-90e9-65f18a8b337d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-04 Thread Mark Duesbury

Sorry should have mentioned...

gwtversion is set to...

2.8.0-rc1


But because there was not a 2.8.0-rc1 version of the gwt-maven-plugin i 
changed the version of the plugin back to 2.8.0-beta1 (should have changed 
it to 2.8.0-SNAPSHOT)


I just changed the version of the gwt-maven-plugin to 2.8.0-SNAPSHOT and 
ran again Still the same out of memory error occurs.


On Friday, August 5, 2016 at 3:05:29 AM UTC+1, Roberto Lublinerman wrote:
>
> The issue was addressed post beta 1. Please use the 2.8rc1 instead.
>
> On Thu, Aug 4, 2016 at 6:57 PM, Mark Duesbury  > wrote:
>
>> Just tried with -Xmx8g (running on 16gb Macbook Pro)
>>
>> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC 
>> overhead limit exceeded
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.createType(
>> ReferenceMapper.java:280)
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.get(
>> ReferenceMapper.java:146)
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createField(
>> GwtAstBuilder.java:3900)
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(
>> GwtAstBuilder.java:3969)
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(
>> GwtAstBuilder.java:3825)
>>
>> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(
>> GwtAstBuilder.java:3860)
>>
>> [ERROR] at 
>> com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(
>> CompilationStateBuilder.java:129)
>>
>> [ERROR] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(
>> JdtCompiler.java:384)
>>
>> [ERROR] at 
>> org.eclipse.jdt.internal.compiler.Compiler.processCompiledUnits(
>> Compiler.java:546)
>>
>> [ERROR] at org.eclipse.jdt.internal.compiler.Compiler.compile(
>> Compiler.java:458)
>>
>> [ERROR] at com.google.gwt.dev.javac.JdtCompiler.doCompile(
>> JdtCompiler.java:1089)
>>
>> [ERROR] at 
>> com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(
>> CompilationStateBuilder.java:325)
>>
>> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(
>> CompilationStateBuilder.java:548)
>>
>> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
>> CompilationStateBuilder.java:479)
>>
>> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
>> CompilationStateBuilder.java:465)
>>
>> [ERROR] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(
>> ModuleDef.java:423)
>>
>> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:222)
>>
>> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
>>
>> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
>>
>> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
>>
>> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
>>
>> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
>>
>> [ERROR] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
>>
>> [ERROR] at com.google.gwt.dev.CompileTaskRunner.doRun(
>> CompileTaskRunner.java:55)
>>
>> [ERROR] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(
>> CompileTaskRunner.java:50)
>>
>> [ERROR] at com.google.gwt.dev.Compiler.main(Compiler.java:125)
>>
>> Full GWT Maven Plugin config
>>
>> 
>>
>> 
>>
>> org.codehaus.mojo
>>
>> gwt-maven-plugin
>>
>> 2.8.0-beta1
>>
>> 
>>
>> 
>>
>> com.google.gwt
>>
>> gwt-user
>>
>> ${gwtversion}
>>
>> 
>>
>> 
>>
>> com.google.gwt
>>
>> gwt-dev
>>
>> ${gwtversion}
>>
>> 
>>
>> 
>>
>> com.google.gwt
>>
>> gwt-servlet
>>
>> ${gwtversion}
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>   -Xms1024M -Xmx8g -Xss1024k
>>
>> 
>>
>> 
>>
>> compile
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> desktop.html
>>
>> ${project.build.directory}/${project.build.finalName}> hostedWebapp>
>>
>> true
>>
>> true
>>
>> true
>>
>> INFO
>>
>> 
>>
>>  
>>
>> It works fine if I switch back to GWT 2.7.0
>>
>> On Thursday, August 4, 2016 at 10:13:40 PM UTC+1, Roberto Lublinerman 
>> wrote:
>>>
>>> You might need to increase the heap size. JDT still uses more memory 
>>> under Java 8 which is the source level that is currently supported by GWT 
>>> (try -Xmx3g or  -Xmx4g). 
>>>
>>> On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury  
>>> wrote:
>>>
 Hi .. Thanks for the rc...

 I have been struggling for a while now with a 
 java.lang.OutOfMemoryError: GC overhead limit exceeded error on 
 compilation 
 since switching to GWT 2.8.0 beta1. I thought and hoped the problem would 
 be solved with the release of the RC, but it hasn't. I have searched high 
 and low on stackoverflow and elsewhere and tried just about every 
 combination of jvm settings I could find.. but nothing works. I dont think 
 my project is that large with 215 source files.

 The last settings I tried were...

 

 

 

 4

   -Xmx2g

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-04 Thread 'Roberto Lublinerman' via GWT Contributors

The issue was addressed post beta 1. Please use the 2.8rc1 instead.

On Thu, Aug 4, 2016 at 6:57 PM, Mark Duesbury 
wrote:

> Just tried with -Xmx8g (running on 16gb Macbook Pro)
>
> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
>
> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.createType(Ref
> erenceMapper.java:280)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.get(ReferenceM
> apper.java:146)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createField(GwtA
> stBuilder.java:3900)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(Gw
> tAstBuilder.java:3969)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(GwtA
> stBuilder.java:3825)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(GwtAstBu
> ilder.java:3860)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder$
> CompileMoreLater$UnitProcessorImpl.process(Comp
> ilationStateBuilder.java:129)
>
> [ERROR] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(
> JdtCompiler.java:384)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.Compiler.
> processCompiledUnits(Compiler.java:546)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.Compiler.compile(Comp
> iler.java:458)
>
> [ERROR] at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompi
> ler.java:1089)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder$
> CompileMoreLater.compile(CompilationStateBuilder.java:325)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(
> CompilationStateBuilder.java:548)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
> CompilationStateBuilder.java:479)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
> CompilationStateBuilder.java:465)
>
> [ERROR] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(
> ModuleDef.java:423)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:222)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
>
> [ERROR] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
>
> [ERROR] at com.google.gwt.dev.CompileTaskRunner.doRun(Compil
> eTaskRunner.java:55)
>
> [ERROR] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(
> CompileTaskRunner.java:50)
>
> [ERROR] at com.google.gwt.dev.Compiler.main(Compiler.java:125)
>
> Full GWT Maven Plugin config
>
> 
>
> 
>
> org.codehaus.mojo
>
> gwt-maven-plugin
>
> 2.8.0-beta1
>
> 
>
> 
>
> com.google.gwt
>
> gwt-user
>
> ${gwtversion}
>
> 
>
> 
>
> com.google.gwt
>
> gwt-dev
>
> ${gwtversion}
>
> 
>
> 
>
> com.google.gwt
>
> gwt-servlet
>
> ${gwtversion}
>
> 
>
> 
>
> 
>
> 
>
> 
>
>   -Xms1024M -Xmx8g -Xss1024k
>
> 
>
> 
>
> compile
>
> 
>
> 
>
> 
>
> 
>
> desktop.html
>
> ${project.build.directory}/${project.build.finalName} hostedWebapp>
>
> true
>
> true
>
> true
>
> INFO
>
> 
>
> 
>
> It works fine if I switch back to GWT 2.7.0
>
> On Thursday, August 4, 2016 at 10:13:40 PM UTC+1, Roberto Lublinerman
> wrote:
>>
>> You might need to increase the heap size. JDT still uses more memory
>> under Java 8 which is the source level that is currently supported by GWT
>> (try -Xmx3g or  -Xmx4g).
>>
>> On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury 
>> wrote:
>>
>>> Hi .. Thanks for the rc...
>>>
>>> I have been struggling for a while now with a
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded error on compilation
>>> since switching to GWT 2.8.0 beta1. I thought and hoped the problem would
>>> be solved with the release of the RC, but it hasn't. I have searched high
>>> and low on stackoverflow and elsewhere and tried just about every
>>> combination of jvm settings I could find.. but nothing works. I dont think
>>> my project is that large with 215 source files.
>>>
>>> The last settings I tried were...
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 4
>>>
>>>   -Xmx2g -Xms1g -Xss1024k
>>>
>>>   true
>>>
>>> 
>>>
>>> 
>>>
>>> compile
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>>
>>> The error occurs at different points in the compile cycle... A few
>>> samples are shown below...
>>>
>>> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC
>>> overhead limit exceeded
>>>
>>> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.BoundSet.(Bou
>>> ndSet.java:308)
>>>
>>> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.
>>> createInitialBoundSet(InferenceContext18.java:230)
>>>
>>> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.ConstraintExpressio
>>>

[gwt-contrib] Re: Documentation site on github

2016-08-04 Thread Kay Pac

I've been unable to find the "JUnit.html" page in the github gwt-site 
depot. The url is: http://www.gwtproject.org/doc/latest/tutorial/JUnit.html

Any help?

On Wednesday, February 11, 2015 at 1:05:11 AM UTC-8, Thomas Broyer wrote:
>
>
>
> On Wednesday, February 11, 2015 at 9:50:34 AM UTC+1, rhmoller wrote:
>>
>> I just tried this out, but it seems there is a difference in the way 
>> github and gwtproject renders markdown.
>>
>> I saw that the bullets on the UIBinder page were not rendered properly, 
>> but on github they look right.
>>
>
> Yes, because there's not "one" markdown (just like there's not "one 
> webkit" or "one chromium" 
> )
> This is why we have http://commonmark.org/ but implementations have not 
> updated to that spec yet (which isn't even finished).
>
> In this case, I think the difference is in whether there should be a blank 
> line before the first bullet or not. See 
> http://spec.commonmark.org/0.17/#example-201
>

-- 
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/a431f485-4334-45c1-a71d-ea8de4f96aa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Documentation site on github

2016-08-04 Thread Kay Pac

I've been unable to find the "JUnit.html" page in the github gwt-site 
depot. The url is: http://www.gwtproject.org/doc/latest/tutorial/JUnit.html

Any help?

On Wednesday, February 11, 2015 at 1:05:11 AM UTC-8, Thomas Broyer wrote:
>
>
>
> On Wednesday, February 11, 2015 at 9:50:34 AM UTC+1, rhmoller wrote:
>>
>> I just tried this out, but it seems there is a difference in the way 
>> github and gwtproject renders markdown.
>>
>> I saw that the bullets on the UIBinder page were not rendered properly, 
>> but on github they look right.
>>
>
> Yes, because there's not "one" markdown (just like there's not "one 
> webkit" or "one chromium" 
> )
> This is why we have http://commonmark.org/ but implementations have not 
> updated to that spec yet (which isn't even finished).
>
> In this case, I think the difference is in whether there should be a blank 
> line before the first bullet or not. See 
> http://spec.commonmark.org/0.17/#example-201
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Using custom servlet for GWT-RPC with GWTTestCase

2016-08-04 Thread Thomas Broyer

On Thursday, August 4, 2016 at 9:26:27 PM UTC+2, Kay Pac wrote:
>
> I guess I am confused. I understand the need to do as much testing as 
> possible with regular JUnit/TestNG tests, which I try to do. What I don't 
> understand precisely is where the area of coverage for GWTTestCase is - 
> it's some area between vanilla JUnit and Selenium/Webdriver, but it's clear 
> I don't understand what that area is or how to take advantage of it. I am 
> certain the structure of my code is a problem - I hacked some bits together 
> and embedded a dependency on a spring gwt webservice, which I can't run 
> within the JUnitShell. It makes sense to remove that dependency and supply 
> a mock object.
>

GWTTestCase is there to test code that needs to run in a "GWT/browser" 
context: widgets, elements, events, super-source, etc. The  is 
used by GWT itself in test FormPanel, RequestBuilder and GWT-RPC, at the 
"protocol" level (i.e. with servlets designed to trigger specific code 
paths in client-side code –and server-side code for GWT-RPC– depending on 
the request).

> Part of my confusion, I believe, stems from the documentation for the 
> gwt-maven-plugin, which says that it considers the GWTTestCase integration 
> tests and not unit tests.
>

The gwt-maven-plugin⋅s are independent projects. Mojo's Maven Plugin for 
GWT categorizes GWTTestCase as integration tests (historically, I believe) 
mainly because they're slow and involve many moving pieces: they're 
undoubtedly "bigger" than "unit" tests.
I, for one, treat them more as unit tests, and my Maven Plugin for GWT 
(net.ltgt.gwt.maven:gwt-maven-plugin) runs them at the "test" phase.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

2016-08-04 Thread Thomas Broyer

This might be due to the optimization level. What if you compile as -draft 
or -optimize 0?
FWIW, GWT tends to get system props in static initialization of constants, 
passing string literals as argument. I.e.
static final String PROP_VALUE = System.getProperty("myProperty");

On Thursday, August 4, 2016 at 9:35:05 PM UTC+2, clou...@gmail.com wrote:
>
> Hi there,
>
> Pretty simple example, but seems like possibly a bug or oddity in GWT 
> 2.8b1 between the command line and the Eclipse plug in.
>
> Setup: In a Module.gwt.xml file we define a property like so:
> 
> 
>
> In a class we use it like so (paraphrased):
> public class MyClass {
>
>public static final String STR_PROP = "myProperty";
>
>
>
> public void foo() {
> String propValue = System.getProperty(STR_PROP);
> 
> }
> }
>
> Behavior difference!
>  - When we compile this on our command line, there is no error.
>  - When we run thru SDM, the following error pops up:  [ERROR] Line 37: 
> Only string constants may be used as property name in System.getProperty()
>
> Does SDM just have an issue with the String constant used whereas the 
> compiler itself does not? Bug? Intended? Suggestions? Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-04 Thread 'Roberto Lublinerman' via GWT Contributors

You might need to increase the heap size. JDT still uses more memory under
Java 8 which is the source level that is currently supported by GWT (try
-Xmx3g or  -Xmx4g).

On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury 
wrote:

> Hi .. Thanks for the rc...
>
> I have been struggling for a while now with a java.lang.OutOfMemoryError:
> GC overhead limit exceeded error on compilation since switching to GWT
> 2.8.0 beta1. I thought and hoped the problem would be solved with the
> release of the RC, but it hasn't. I have searched high and low on
> stackoverflow and elsewhere and tried just about every combination of jvm
> settings I could find.. but nothing works. I dont think my project is that
> large with 215 source files.
>
> The last settings I tried were...
>
> 
>
> 
>
> 
>
> 4
>
>   -Xmx2g -Xms1g -Xss1024k
>
>   true
>
> 
>
> 
>
> compile
>
> 
>
> 
>
> 
>
>
> The error occurs at different points in the compile cycle... A few samples
> are shown below...
>
> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.BoundSet.(
> BoundSet.java:308)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.
> createInitialBoundSet(InferenceContext18.java:230)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.
> ConstraintExpressionFormula.inferInvocationApplicability(C
> onstraintExpressionFormula.java:336)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.
> inferInvocationApplicability(InferenceContext18.java:370)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.
> ParameterizedGenericMethodBinding.computeCompatibleMethod18(
> ParameterizedGenericMethodBinding.java:233)
>
>
>
> --
> 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/1c185f70-edf4-
> 4e54-9cfe-48b7908d54ba%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3Dx45KNani6eccA9MUejj%2BGNOOPcduVaf%3D-Gx9b0fQxhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

2016-08-04 Thread Thomas Broyer

Goktug: my reading of JsInterop is that @JsType(isNative=true) types 
shouldn't have non-annotated non-public members: either they're "mapped" 
properties and methods and should be public or annotated with @JsMethod or 
@JsProperty, or they're @JsOverlay methods; and there shouldn't be 
@JsIgnore'd members as well. If this is exact, then maybe the compiler 
should complain.
+1 for seeing a repro sample though, as the snippet wouldn't work anyway 
(to begin with, uses @JsNative instead of @JsType)

On Thursday, August 4, 2016 at 9:33:04 PM UTC+2, Goktug Gokdogan wrote:
>
> I'm not sure what you mean by working fine. If animal doesn't exist in the 
> object; it is expected to fail. Can you provide a full repro example?
>
> On Thu, Aug 4, 2016 at 2:50 AM, Teletin Alin  
> wrote:
>
>> Hi,
>>
>> I do have a problem since moving to rc1 related to a map object.
>> Using beta1 the code works ok, but with rc1 it yields 
>> "this.static$.animals.put is not a function".
>>
>> Example code:
>>
>> @JsNative(isNative = true, namespace="Example.com", name="Person")
>> public class Person{
>>
>> @JsProperty(name = "name")
>> public String name;
>> @JsProperty(name = "age")
>> public int age;
>>
>> private Map animals; //an extra property that is 
>> not found in javascript
>>
>> public native boolean isOld();
>>
>> @JsOverlay
>> public final void buyAnimal(Animal animal){ // I don't know if it 
>> matters, but Animal object is also native as Person
>> String animalName = animal.getName();
>> animals.put(animalName, animal); // this fails with 
>> "this.static$.animals.put is not a function"
>> }
>> }
>>
>> The above code works fine when using beta1.
>> Is there some documentation related to differences between rc1 and 
>> beta1(at least related to jsinterop)?
>> *What other changes should I make when moving to rc1?*
>>
>> My pom file contains:
>> ...
>> 
>> ...
>> 1.8
>> 2.8.0-rc1
>> 
>> 2.8.0-SNAPSHOT
>> 1.0.0-SNAPSHOT
>> ...
>> 
>> ...
>> 
>> org.codehaus.mojo
>> gwt-maven-plugin
>> ${gwt.maven.plugin.version}
>> 
>> ${java.version}
>> ${java.version}
>> true
>> ${gwt.style}
>>
>> -Xmx2048m -Xss1024k -XX:MaxPermSize=256m
>> ${webappDirectory}
>> ${superDevMode}
>> true
>> ...
>> ...
>> htmlunit
>> 
>> 
>> 
>> compile
>> 
>> compile
>> 
>> 
>> 
>> run
>> 
>> run
>> 
>> 
>> 
>> test
>> 
>> test
>> 
>> 
>> **/GwtTestSuite*.java
>> 
>> 
>> 
>> 
>> ...
>> 
>> ...
>> 
>> 
>> com.google.gwt
>> gwt-servlet
>> 
>> 
>> com.google.gwt
>> gwt-user
>> provided
>> 
>> 
>> com.google.gwt
>> gwt-dev
>> provided
>> 
>> 
>> com.google.gwt
>> gwt-codeserver
>> provided
>> 
>> ...
>> 
>> ...
>>
>> Thank you,
>>
>> -- 
>> 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/0d7bb6ac-a184-4c55-a6f0-f09af725a82a%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/44347e9e-13c2-4bc4-b063-5fdfa93cd478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

2016-08-04 Thread cloud450

Hi there,

Pretty simple example, but seems like possibly a bug or oddity in GWT 2.8b1 
between the command line and the Eclipse plug in.

Setup: In a Module.gwt.xml file we define a property like so:



In a class we use it like so (paraphrased):
public class MyClass {
   
   public static final String STR_PROP = "myProperty";

   

public void foo() {
String propValue = System.getProperty(STR_PROP);

}
}

Behavior difference!
 - When we compile this on our command line, there is no error.
 - When we run thru SDM, the following error pops up:  [ERROR] Line 37: 
Only string constants may be used as property name in System.getProperty()

Does SDM just have an issue with the String constant used whereas the 
compiler itself does not? Bug? Intended? Suggestions? Thanks!

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

2016-08-04 Thread 'Goktug Gokdogan' via GWT Contributors

I'm not sure what you mean by working fine. If animal doesn't exist in the
object; it is expected to fail. Can you provide a full repro example?

On Thu, Aug 4, 2016 at 2:50 AM, Teletin Alin 
wrote:

> Hi,
>
> I do have a problem since moving to rc1 related to a map object.
> Using beta1 the code works ok, but with rc1 it yields
> "this.static$.animals.put is not a function".
>
> Example code:
>
> @JsNative(isNative = true, namespace="Example.com", name="Person")
> public class Person{
>
> @JsProperty(name = "name")
> public String name;
> @JsProperty(name = "age")
> public int age;
>
> private Map animals; //an extra property that is
> not found in javascript
>
> public native boolean isOld();
>
> @JsOverlay
> public final void buyAnimal(Animal animal){ // I don't know if it
> matters, but Animal object is also native as Person
> String animalName = animal.getName();
> animals.put(animalName, animal); // this fails with
> "this.static$.animals.put is not a function"
> }
> }
>
> The above code works fine when using beta1.
> Is there some documentation related to differences between rc1 and
> beta1(at least related to jsinterop)?
> *What other changes should I make when moving to rc1?*
>
> My pom file contains:
> ...
> 
> ...
> 1.8
> 2.8.0-rc1
> 2.8.0-SNAPSHOT version>
> 1.0.0-SNAPSHOT
> ...
> 
> ...
> 
> org.codehaus.mojo
> gwt-maven-plugin
> ${gwt.maven.plugin.version}
> 
> ${java.version}
> ${java.version}
> true
> ${gwt.style}
>
> -Xmx2048m -Xss1024k -XX:MaxPermSize=256m
> ${webappDirectory}
> ${superDevMode}
> true
> ...
> ...
> htmlunit
> 
> 
> 
> compile
> 
> compile
> 
> 
> 
> run
> 
> run
> 
> 
> 
> test
> 
> test
> 
> 
> **/GwtTestSuite*.java
> 
> 
> 
> 
> ...
> 
> ...
> 
> 
> com.google.gwt
> gwt-servlet
> 
> 
> com.google.gwt
> gwt-user
> provided
> 
> 
> com.google.gwt
> gwt-dev
> provided
> 
> 
> com.google.gwt
> gwt-codeserver
> provided
> 
> ...
> 
> ...
>
> Thank you,
>
> --
> 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/0d7bb6ac-a184-
> 4c55-a6f0-f09af725a82a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0VNa-Zx-FyGPypLAD0iaFrn7z88RF2p%2BMgNUHo9G%2Bhuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using custom servlet for GWT-RPC with GWTTestCase

2016-08-04 Thread Kay Pac

I guess I am confused. I understand the need to do as much testing as 
possible with regular JUnit/TestNG tests, which I try to do. What I don't 
understand precisely is where the area of coverage for GWTTestCase is - 
it's some area between vanilla JUnit and Selenium/Webdriver, but it's clear 
I don't understand what that area is or how to take advantage of it. I am 
certain the structure of my code is a problem - I hacked some bits together 
and embedded a dependency on a spring gwt webservice, which I can't run 
within the JUnitShell. It makes sense to remove that dependency and supply 
a mock object.

Part of my confusion, I believe, stems from the documentation for the 
gwt-maven-plugin, which says that it considers the GWTTestCase integration 
tests and not unit tests. Thus I categorize them so, and rush to try and 
integrate the kitchen sink. So your suggestions have helped to clear up 
this misunderstanding on my part, I appreciate this clarification, Thank 
you Thomas.

On Thursday, August 4, 2016 at 4:30:43 AM UTC-7, Thomas Broyer wrote:
>
> JUnitShell support for  is not meant for integration tests. You 
> probably shouldn't try to use it that way. Either start a separate server 
> (using CORS), or don't use a GWTTestCase (possibly use a dedicated GWT app 
> and drive it through Selenium/WebDriver.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0-rc1 and closure compiler

2016-08-04 Thread Slava Pankov

IMO it was a bad idea to eliminate closure compiler from GWT, I've always 
used it and usually get 5-10% smaller output.
It's still possible to use, but "manually". I'm building with PRETTY 
option, then unzip war file, process all *.cache.js with closure compiler 
and put them back to war file.
Not sure it's stable though, still have no enough time to test 
it thoroughly.

On Thursday, August 4, 2016 at 9:33:54 AM UTC-7, Luis Fernando Planella 
Gonzalez wrote:
>
> Em quinta-feira, 4 de agosto de 2016 12:03:04 UTC-3, Thomas Broyer 
> escreveu:
>>
>>
>>
>> On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella 
>> Gonzalez wrote:
>>>
>>> I've always used the closure compiler with past versions (even with 
>>> 2.8.0-beta1, which we have used in production already).
>>> Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as 
>>> there's no mention to it in the release notes (
>>> http://www.gwtproject.org/release-notes.html).
>>>
>>
>> We may want to add a note about it; but that was an experimental feature 
>> and those tend to come and go as experiments prove their value or not.
>> See 
>> https://gwt.googlesource.com/gwt/+/162ccc9c9112a09bf9ea046da95760f5f1886b72%5E%21/
>>  
>> for the rationale.
>>
>
> Ok. In our project, we used to enable the closure compiler because the 
> codebase is quite large, and closure compiler helped in reducing further 
> the code size. I don't have the numbers at hand, but the full code size 
> (including all split points) is about 2.8M, and closure compiler reduced 
> some hundred kilobytes from it.
>  
>
>>  
>>
>>> Now the compiler no longer supports the old closure compiler option, but 
>>> has a new -X[no]closureFormattedOutput option.
>>>
>>
>> It's not really new actually: 
>> https://gwt.googlesource.com/gwt/+/6fa611cf9ad7ffa077a7378a100a7ccbd95e3cb3%5E%21/
>>
>
> I have assumed it was new because it is not present as option in the 
> gwt-maven-plugin (which is updated up to the beta1).
>
>  
>>
>>> I'm guessing closure compiler is no longer integrated in GWT, but it 
>>> still has the option to format for closure to a later (manual) usage of 
>>> closure compiler.
>>> I'm using the gwt-maven-plugin, which still uses beta1, but explicitly 
>>> changing its dependencies to 2.8.0-rc1 for gwt-user, gwt-dev and 
>>> gwt-codeserver artifacts, making it usable already for rc1.
>>> I can't, however, pass the new option (I think there's no way to pass 
>>> arbitrary compiler arguments with gwt-maven-plugin) until the maven plugin 
>>> is updated.
>>>
>>> What are the new instructions to keep using closure compiler?
>>>
>>
>> There aren't (see comment about -XclosureFormattedOutput in the commit 
>> message that introduced it)
>> Do you really *need* it?
>>
>
> I was assuming that flag was needed in order to generate code that 
> complies with the closure compiler limitations (
> https://developers.google.com/closure/compiler/docs/limitations).
> Maybe that is not the case and I can just invoke the closure compiler 
> manually on the generated GWT code? Should I expect any runtime problems by 
> doing this?
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0-rc1 and closure compiler

2016-08-04 Thread Luis Fernando Planella Gonzalez

Em quinta-feira, 4 de agosto de 2016 12:03:04 UTC-3, Thomas Broyer escreveu:
>
>
>
> On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella 
> Gonzalez wrote:
>>
>> I've always used the closure compiler with past versions (even with 
>> 2.8.0-beta1, which we have used in production already).
>> Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as 
>> there's no mention to it in the release notes (
>> http://www.gwtproject.org/release-notes.html).
>>
>
> We may want to add a note about it; but that was an experimental feature 
> and those tend to come and go as experiments prove their value or not.
> See 
> https://gwt.googlesource.com/gwt/+/162ccc9c9112a09bf9ea046da95760f5f1886b72%5E%21/
>  
> for the rationale.
>

Ok. In our project, we used to enable the closure compiler because the 
codebase is quite large, and closure compiler helped in reducing further 
the code size. I don't have the numbers at hand, but the full code size 
(including all split points) is about 2.8M, and closure compiler reduced 
some hundred kilobytes from it.
 

>  
>
>> Now the compiler no longer supports the old closure compiler option, but 
>> has a new -X[no]closureFormattedOutput option.
>>
>
> It's not really new actually: 
> https://gwt.googlesource.com/gwt/+/6fa611cf9ad7ffa077a7378a100a7ccbd95e3cb3%5E%21/
>

I have assumed it was new because it is not present as option in the 
gwt-maven-plugin (which is updated up to the beta1).

 
>
>> I'm guessing closure compiler is no longer integrated in GWT, but it 
>> still has the option to format for closure to a later (manual) usage of 
>> closure compiler.
>> I'm using the gwt-maven-plugin, which still uses beta1, but explicitly 
>> changing its dependencies to 2.8.0-rc1 for gwt-user, gwt-dev and 
>> gwt-codeserver artifacts, making it usable already for rc1.
>> I can't, however, pass the new option (I think there's no way to pass 
>> arbitrary compiler arguments with gwt-maven-plugin) until the maven plugin 
>> is updated.
>>
>> What are the new instructions to keep using closure compiler?
>>
>
> There aren't (see comment about -XclosureFormattedOutput in the commit 
> message that introduced it)
> Do you really *need* it?
>

I was assuming that flag was needed in order to generate code that complies 
with the closure compiler limitations 
(https://developers.google.com/closure/compiler/docs/limitations).
Maybe that is not the case and I can just invoke the closure compiler 
manually on the generated GWT code? Should I expect any runtime problems by 
doing this?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: 2.8rc1 and server reload in Intellij

2016-08-04 Thread Thomas Broyer

Reproduced. I have a fix: https://gwt-review.googlesource.com/15500

We probably need to add this ("restart web server") to our smoke test 
process.

On Thursday, August 4, 2016 at 9:19:08 AM UTC+2, P.G.Taboada wrote:
>
> Hi,
>
> with GWT 2.8 I cannot reload the server anymore:
>
> java.util.concurrent.RejectedExecutionException: 
> org.eclipse.jetty.annotations.AnnotationConfiguration$1@2a5ec0a4
> at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.execute(QueuedThreadPool.java:362)
> at 
> org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:541)
> at 
> org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:447)
> at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:479)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1337)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
>
>
> Am I the only one? 
>
> brgds,
>
> Papick
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Bean Validation

2016-08-04 Thread Manfred Tremmel

Am Donnerstag, 4. August 2016, 14:19:31 schrieb Colin Alworth:

> What maven repo has the SNAPSHOT in it?

It's in Sonatype Nexus Snapshots:
https://oss.sonatype.org/content/repositories/snapshots/de/knightsoft-net/gwt-bean-validators/0.19.0-SNAPSHOT/

should be available in central without adding something special in the pom.xml.

> Is https://github.com/ManfredTremmel/gwt-bean-validators the source
> for this?

Yes.

Including bean validation routine from gwt project:
https://github.com/ManfredTremmel/gwt-bean-validators/commit/c0bf4e57ea9200e41c23f1351636d92243c2c609
https://github.com/ManfredTremmel/gwt-bean-validators/commit/8d10e62ff666a499490a40b50bf8909ed01dafcb

Migration of the api (yes, It was a real big commit):
https://github.com/ManfredTremmel/gwt-bean-validators/commit/4600230efb15f176f91b15d06d0ffa39bfda1feb


> Great work, looking forward to putting this to use, and
> porting it to annotation processors for long-term GWT support!

If interested, I can backport it to the GWT project for 2.8.1 or so.
This was the Idea why I've started this thread a month ago.
As I understood Thomas Broyer, there was no interest to update validation
in gwt, as it should be removed in future versions

> I'm working with Frank Hossfeld on porting Editors to APT as well,
> perhaps we can work together to provide the extra functionality you
> require to be exposed from drivers.

I'm glad with Editor functionality. I've created my own driver
(BeanValidationEditorDriver) to automate validation, as you
can read on the wiki page (Topic "Client side validation") on
https://github.com/ManfredTremmel/gwt-bean-validators-example/wiki/Client-Implementation
and test on https://www.knightsoft-net.de/validationexample/
If you are interested in adding some of the functionality, I'm glad to
help you

-- 
Machs gut| http://www.iivs.de/schwinde/buerger/tremmel/
 | https://github.com/ManfredTremmel
Manfred  | http://www.knightsoft-net.de

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

Re: [gwt-contrib] Re: Bean Validation

2016-08-04 Thread Thomas Broyer



On Thursday, August 4, 2016 at 4:19:50 PM UTC+2, Colin Alworth wrote:
>
> What maven repo has the SNAPSHOT in it? 
>

Sonatype 
OSSRH? 
https://github.com/ManfredTremmel/gwt-bean-validators/blob/4600230efb15f176f91b15d06d0ffa39bfda1feb/pom.xml#L57-L68

-- 
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/88f2059b-9eda-424e-ade0-009c0067da35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0-rc1 and closure compiler

2016-08-04 Thread Thomas Broyer



On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella 
Gonzalez wrote:
>
> I've always used the closure compiler with past versions (even with 
> 2.8.0-beta1, which we have used in production already).
> Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as 
> there's no mention to it in the release notes (
> http://www.gwtproject.org/release-notes.html).
>

We may want to add a note about it; but that was an experimental feature 
and those tend to come and go as experiments prove their value or not.
See 
https://gwt.googlesource.com/gwt/+/162ccc9c9112a09bf9ea046da95760f5f1886b72%5E%21/
 
for the rationale.
 

> Now the compiler no longer supports the old closure compiler option, but 
> has a new -X[no]closureFormattedOutput option.
>

It's not really new 
actually: 
https://gwt.googlesource.com/gwt/+/6fa611cf9ad7ffa077a7378a100a7ccbd95e3cb3%5E%21/
 

> I'm guessing closure compiler is no longer integrated in GWT, but it still 
> has the option to format for closure to a later (manual) usage of closure 
> compiler.
> I'm using the gwt-maven-plugin, which still uses beta1, but explicitly 
> changing its dependencies to 2.8.0-rc1 for gwt-user, gwt-dev and 
> gwt-codeserver artifacts, making it usable already for rc1.
> I can't, however, pass the new option (I think there's no way to pass 
> arbitrary compiler arguments with gwt-maven-plugin) until the maven plugin 
> is updated.
>
> What are the new instructions to keep using closure compiler?
>

There aren't (see comment about -XclosureFormattedOutput in the commit 
message that introduced it)
Do you really *need* it?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

2016-08-04 Thread Teletin Alin

Hi,

I do have a problem since moving to rc1 related to a map object.
Using beta1 the code works ok, but with rc1 it yields 
"this.static$.animals.put is not a function".

Example code:

@JsNative(isNative = true, namespace="Example.com", name="Person")
public class Person{

@JsProperty(name = "name")
public String name;
@JsProperty(name = "age")
public int age;

private Map animals; //an extra property that is 
not found in javascript

public native boolean isOld();

@JsOverlay
public final void buyAnimal(Animal animal){ // I don't know if it 
matters, but Animal object is also native as Person
String animalName = animal.getName();
animals.put(animalName, animal); // this fails with 
"this.static$.animals.put is not a function"
}
}

The above code works fine when using beta1.
Is there some documentation related to differences between rc1 and beta1(at 
least related to jsinterop)?
*What other changes should I make when moving to rc1?*

My pom file contains:
...

...
1.8
2.8.0-rc1
2.8.0-SNAPSHOT
1.0.0-SNAPSHOT
...

...

org.codehaus.mojo
gwt-maven-plugin
${gwt.maven.plugin.version}

${java.version}
${java.version}
true
${gwt.style}

-Xmx2048m -Xss1024k -XX:MaxPermSize=256m
${webappDirectory}
${superDevMode}
true
...
...
htmlunit



compile

compile



run

run



test

test


**/GwtTestSuite*.java




...

...


com.google.gwt
gwt-servlet


com.google.gwt
gwt-user
provided


com.google.gwt
gwt-dev
provided


com.google.gwt
gwt-codeserver
provided

...

...

Thank you,

-- 
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/0d7bb6ac-a184-4c55-a6f0-f09af725a82a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Bean Validation

2016-08-04 Thread Colin Alworth

What maven repo has the SNAPSHOT in it?

Is https://github.com/ManfredTremmel/gwt-bean-validators the source for
this? Great work, looking forward to putting this to use, and porting it to
annotation processors for long-term GWT support!

I'm working with Frank Hossfeld on porting Editors to APT as well, perhaps
we can work together to provide the extra functionality you require to be
exposed from drivers.

On Thu, Aug 4, 2016 at 9:12 AM ManfredTremmel 
wrote:

> For your information, I've just commited a new gwt-bean-validators
> snapshot, it now:
>
>
>- includes complete validation implementation (ported from gwt
>implementation, so if it'll be removed from gwt it should still work)
>- switched validation-api from 1.0.0.GA to 1.1.0.Final
>- switched hibernate-validator from 4.1.0.Final to 5.2.4.Final
>- reworked validation implementation to work together with new api
>- added some gwt implementations of incompatible
>hibernate-validator 5.2.4 validation routines
>
> It's not ready to release, but if anybody is interested in testing, it can
> be done now. I've also uploaded to maven repository:
>
>
> What to do to let a project use it?
>
>
>
>1. Add the maven dependency:
>
>de.knightsoft-net
>gwt-bean-validators
>0.19.0-SNAPSHOT
>
>
>2. Add/Replace versions in maven configurations of validation-api
>to 1.1.0.Final and hibernate-validator to 5.2.4.Final
>3. In the *.gwt.xml Configuration, replace
>
>
>with
>
>
>4. Replace "com.google.gwt.validation" with
>"de.knightsoftnet.validators" in the project
>
> I've build with gwt 2.7.0, also tested with 2.8.0-rc1 and all my 235
> gwt-unit-tests have passed.
>
> --
> 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/ffe8a4b9-fb83-4f38-94d5-2fcb63b026e8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CADcXZMwCJHF_cqCP23_X5RKv1DQ37N0RZ8bs4iidXVEQNZhu4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.8.0 RC1 is here!

2016-08-04 Thread Frank

I fixed this by removing the reference to Logger in my own Level class.

Now all seems to be working ok :-)


Op woensdag 3 augustus 2016 16:46:15 UTC+2 schreef Frank:
>
> Hi Jens,
>
> Thanks for the quick response.
>
> I will try to explain what I needed, and what I did...
>
>
> I needed to have the following loglevels : ERROR and EXCEPTION. I asked 
> this I think in this Google Group when I needed it but the only reply I got 
> was that this was not possible.
> In the end I found out that if I created a super-source ( path="super"/>) I could override the default GWT implementation of classes.
>
> So what I did is I copied the java.util.logging.Level class from the GWT 
> source tree, and modified it by adding my two needed levels.
>
> This however gave compilation errors because methods from java.util.Logger 
> where called that are not available in the rt.jar version of 
> java.util.Logger.
> So I just copied the java.util.Logger from the GWT source tree to my own 
> project.
> I just kept doing this until everything worked. In the end I copied 
> Logger.java, LogManager.java and SimpleConsoleLogHandler.java to my own 
> project and everything worked without a problem.
>
> But now when I upgrade to RC1 I get a compilation error in 
> SimpleConsoleLogHandler.java that it can not find 
>  javaemul.internal.ConsoleLogger. 
> Now I did try to copy this class into my own project, but this then needs 
> other files, which in their turn need again other files. Maybe if I copy 
> the complete GWT super source code to my own project I will get it to work. 
> But that is not really a good way to work I think, and hard to maintain.
>
>
> Is there maybe a way that I just put Level.java in my own project. And do 
> something so that it knows not to look for java.util.Logger in rt.jar, but 
> in gwt-dev.jar or gwt-user.jar ?
>
>
>
>
>
>
>
> Op woensdag 3 augustus 2016 16:14:42 UTC+2 schreef Jens:
>>
>>
>> Why is this the case ? 
>>>
>>
>> It relies on internal API and because of this it can not be compiled 
>> using javac (ConsoleLogger calls Throwable.getBackingJsObject() which does 
>> not exist in JRE so you can not javac the file). The super sourced code is 
>> still present in com/google/gwt/emul/javaemul/internal.
>>
>>  
>>
>>> And any way how I can get work my way around this ?
>>>
>>
>> I don't know what exactly you have done but if nothing helps, copy the 
>> code and adjust it to your needs.
>>
>>
>> -- J.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Bean Validation

2016-08-04 Thread ManfredTremmel

For your information, I've just commited a new gwt-bean-validators
snapshot, it now:

- includes complete validation implementation (ported from gwt
implementation, so if it'll be removed from gwt it should still work)
- switched validation-api from 1.0.0.GA to 1.1.0.Final
- switched hibernate-validator from 4.1.0.Final to 5.2.4.Final
- reworked validation implementation to work together with new api
- added some gwt implementations of incompatible
hibernate-validator 5.2.4 validation routines

It's not ready to release, but if anybody is interested in testing, it can
be done now. I've also uploaded to maven repository:

What to do to let a project use it?

1. Add the maven dependency:

de.knightsoft-net
gwt-bean-validators
0.19.0-SNAPSHOT

2. Add/Replace versions in maven configurations of validation-api
to 1.1.0.Final and hibernate-validator to 5.2.4.Final
3. In the *.gwt.xml Configuration, replace

with

4. Replace "com.google.gwt.validation" with
"de.knightsoftnet.validators" in the project

I've build with gwt 2.7.0, also tested with 2.8.0-rc1 and all my 235
gwt-unit-tests have passed.

--
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/ffe8a4b9-fb83-4f38-94d5-2fcb63b026e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.8.0 RC1 is here!

2016-08-04 Thread Frank

I managed to fix this issue by removing dependencies to Logger from my own 
Level class.

Now I have the following issue.
When I try to run my application I get the following :

run:
 [java] Super Dev Mode starting up
 [java]workDir: 
C:\Users\frank\AppData\Local\Temp\gwt-codeserver-6018982024449493766.tmp
 [java]Loading inherited module 'be.fwy.gwt.Arpol'
 [java]   Loading inherited module 'com.google.gwt.core.Core'
 [java]  Loading inherited module 
'com.google.gwt.emul.Emulation'
 [java] Loading inherited module 
'javaemul.internal.Internal'
 [java][ERROR] Unable to find 
'javaemul/internal/Internal.gwt.xml' on your classpath; could be a typo, or 
maybe you forgot to include a classpath entry for source?


I have no idea from where this "Loading inherited module 
'com.google.gwt.core.Core'" is coming. I have nowhere an inherit in a 
.gwt.xml file of this module

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT 2.8.0-rc1 and closure compiler

2016-08-04 Thread Luis Fernando Planella Gonzalez

I've always used the closure compiler with past versions (even with 
2.8.0-beta1, which we have used in production already).
Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as there's 
no mention to it in the release notes 
(http://www.gwtproject.org/release-notes.html).

Now the compiler no longer supports the old closure compiler option, but 
has a new -X[no]closureFormattedOutput option.
I'm guessing closure compiler is no longer integrated in GWT, but it still 
has the option to format for closure to a later (manual) usage of closure 
compiler.
I'm using the gwt-maven-plugin, which still uses beta1, but explicitly 
changing its dependencies to 2.8.0-rc1 for gwt-user, gwt-dev and 
gwt-codeserver artifacts, making it usable already for rc1.
I can't, however, pass the new option (I think there's no way to pass 
arbitrary compiler arguments with gwt-maven-plugin) until the maven plugin 
is updated.

What are the new instructions to keep using closure compiler?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Using custom servlet for GWT-RPC with GWTTestCase

2016-08-04 Thread Thomas Broyer

JUnitShell support for  is not meant for integration tests. You 
probably shouldn't try to use it that way. Either start a separate server 
(using CORS), or don't use a GWTTestCase (possibly use a dedicated GWT app and 
drive it through Selenium/WebDriver.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Amazon Web Services / Continuous Integration

2016-08-04 Thread Frisco Software

Thanks, already resolved.

On Thu, Aug 4, 2016 at 3:48 AM, abdul  wrote:

> Hi phil,
>
> Build ear/war from your GWT application to deploy it into AWS
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-web-toolkit/rDnbKxqDEdw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Amazon Web Services / Continuous Integration

2016-08-04 Thread abdul

Hi phil,

Build ear/war from your GWT application to deploy it into AWS

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

2.8rc1 and server reload in Intellij

2016-08-04 Thread P.G.Taboada

Hi,

with GWT 2.8 I cannot reload the server anymore:

java.util.concurrent.RejectedExecutionException: 
org.eclipse.jetty.annotations.AnnotationConfiguration$1@2a5ec0a4
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.execute(QueuedThreadPool.java:362)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:541)
at 
org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:447)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:479)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1337)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)


Am I the only one? 

brgds,

Papick

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

[gwt-contrib] Re: Documentation site on github

Re: Documentation site on github

Re: Using custom servlet for GWT-RPC with GWTTestCase

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

Re: [gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

Re: [gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

Re: Using custom servlet for GWT-RPC with GWTTestCase

Re: GWT 2.8.0-rc1 and closure compiler

Re: GWT 2.8.0-rc1 and closure compiler

Re: 2.8rc1 and server reload in Intellij

Re: [gwt-contrib] Re: Bean Validation

Re: [gwt-contrib] Re: Bean Validation

Re: GWT 2.8.0-rc1 and closure compiler

[gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

Re: [gwt-contrib] Re: Bean Validation

Re: 2.8.0 RC1 is here!

[gwt-contrib] Re: Bean Validation

Re: 2.8.0 RC1 is here!

GWT 2.8.0-rc1 and closure compiler

Re: Using custom servlet for GWT-RPC with GWTTestCase

Re: Amazon Web Services / Continuous Integration

Re: Amazon Web Services / Continuous Integration

2.8rc1 and server reload in Intellij

28 matches

Site Navigation

Mail list logo

Footer information