Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev
So, what does the latest GPE do now? Can we revert the change and go back to what we had in 2.6 (and beta1) with SDM in its own gwt-codeserver.jar and *not* in gwt-dev.jar? (and what about IntelliJ IDEA? I must confess I haven't done any GWT dev –even bug repro checks– for a few weeks, and haven't actually launched DevMode from Eclipse for a while – last things I did were about Maven only) On Sunday, November 2, 2014 8:57:29 PM UTC+1, Brandon Donnelson wrote: This is a bit tricker to deal with in the GPE source than I imagined. The current GPE patch is looking ready to go, but it validates checking for CodeServer in the classpath if SDM is turned on. Although it adds gwt-codeserver.jar to the GWT_CONTAINER resolved classpath. If the gwt-codeserver.jar stays int the gwt-sdk moving forward this isn't an issue, although, if it doesn't the consistency between 2.5 to 2.7 will be different. This creates a challenge with testing in GPE because now that I've added validation, I have to change the unit tests around and it only has one GWT_ROOT, based on the latest sdk, which means the older SDK would need gwt-codeserver.jar and the newer won't. I think GPE plugin update could release first of next week, this could fix the need to fold it into gwt-dev and keep things simpler as it is now. I think I'm going to hold off on the GPE fold into gwt-dev changes until next week and see how the release looks. Brandon On Wednesday, October 29, 2014 9:35:14 AM UTC-7, Brian Slesinsky wrote: It looks like the gwt-codeserver jar will still exist, but the same classes will also be in gwt-dev.jar. So it's ugly but should be backward compatible? - Brian -- 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/92bd06ee-07a9-46d3-b8f9-5518c6882aa9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Not able to run any GWTTestCase
I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) I'm sure something is wrong locally but I don't see what. Any hint ? 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%3D66%3DKJkw6JW%3D4Lyk%2BPNkD6z_PMyqQp2zW%3D9ggVTjoVDrA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Build gwtproject?
Cool nice job. On Thursday, November 13, 2014 5:52:30 AM UTC-8, Julien Dramaix wrote: I've updated the site-uploader in order to upload the dtd files. They should be available now. I have still to modify the application in order to set the right mime-type for the dtd files. Julien On Thu Nov 13 2014 at 12:14:45 AM Brandon Donnelson branfl...@gmail.com javascript: wrote: Ok sounds good, will get that out shortly. On Wednesday, November 12, 2014 12:06:17 PM UTC-8, Julien Dramaix wrote: yep sure, every improvement is welcome ! On Wed Nov 12 2014 at 4:41:32 PM Brandon Donnelson branfl...@gmail.com wrote: I did an uploader rewrite a while back to upload all the files and this also serves them through the servlet if you're interested in that code I can share? On Wednesday, November 12, 2014 6:47:12 AM UTC-8, Julien Dramaix wrote: Yes we have to modify the gwt-site-uploader to uplaod the .dtd files. I will try to spent some time on that tonight. On Wed Nov 12 2014 at 3:32:58 PM Thomas Broyer t.br...@gmail.com wrote: On Wednesday, November 12, 2014 11:38:44 AM UTC+1, Jens wrote: I'm not seeing the http://www.gwtproject.org/ doctype/2.7.0/gwt-module.dtd resources. Either they have been updated, or I configured the assembly wrong and there not getting copied in the build to generated site. Ping. Still doesn't seem to be uploaded yet? The patch has been merged more than a month a ago ( https://gwt-review.googlesource.com/9478) so I think it's rather a bug in the packaging/deployment/file-serving that maybe filters out *.dtd files. -- 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/6f22cf6a-d0f4-4251-81d2- 0b98bd21e69e%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/6f22cf6a-d0f4-4251-81d2-0b98bd21e69e%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+unsubscribe@ googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/google-web-toolkit-contributors/c917c381-15fd- 465e-9409-53604c00a1fb%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/c917c381-15fd-465e-9409-53604c00a1fb%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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/507f8c0e-0f65-4a05-a786-1fe2c9ad36b5%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/507f8c0e-0f65-4a05-a786-1fe2c9ad36b5%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/f7f79dcd-81e1-48cf-b3b2-00a2e8cf425b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev
GPE uses gwt-codeserver.jar in the GWT_CONTAINER and it asks the user to add it to the classpath if it doesn't exist and super dev mode is on. I think idea uses the gwt-codeserver.jar in the runtime classpath but I haven't confirmed. On Friday, November 14, 2014 1:50:13 AM UTC-8, Thomas Broyer wrote: So, what does the latest GPE do now? Can we revert the change and go back to what we had in 2.6 (and beta1) with SDM in its own gwt-codeserver.jar and *not* in gwt-dev.jar? (and what about IntelliJ IDEA? I must confess I haven't done any GWT dev –even bug repro checks– for a few weeks, and haven't actually launched DevMode from Eclipse for a while – last things I did were about Maven only) On Sunday, November 2, 2014 8:57:29 PM UTC+1, Brandon Donnelson wrote: This is a bit tricker to deal with in the GPE source than I imagined. The current GPE patch is looking ready to go, but it validates checking for CodeServer in the classpath if SDM is turned on. Although it adds gwt-codeserver.jar to the GWT_CONTAINER resolved classpath. If the gwt-codeserver.jar stays int the gwt-sdk moving forward this isn't an issue, although, if it doesn't the consistency between 2.5 to 2.7 will be different. This creates a challenge with testing in GPE because now that I've added validation, I have to change the unit tests around and it only has one GWT_ROOT, based on the latest sdk, which means the older SDK would need gwt-codeserver.jar and the newer won't. I think GPE plugin update could release first of next week, this could fix the need to fold it into gwt-dev and keep things simpler as it is now. I think I'm going to hold off on the GPE fold into gwt-dev changes until next week and see how the release looks. Brandon On Wednesday, October 29, 2014 9:35:14 AM UTC-7, Brian Slesinsky wrote: It looks like the gwt-codeserver jar will still exist, but the same classes will also be in gwt-dev.jar. So it's ugly but should be backward compatible? - Brian -- 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/38ce7408-04b1-42db-a0f0-21e07ad1edf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Not able to run any GWTTestCase
On the run rght now, but john merged a patch in that area yesterday, can you try reverting that one? On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com wrote: I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) I'm sure something is wrong locally but I don't see what. Any hint ? 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 javascript:_e(%7B%7D,'cvml','google-web-toolkit-contributors%2bunsubscr...@googlegroups.com'); . To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D66%3DKJkw6JW%3D4Lyk%2BPNkD6z_PMyqQp2zW%3D9ggVTjoVDrA%40mail.gmail.com
Re: [gwt-contrib] Not able to run any GWTTestCase
I have this problem for several days in fact. It's why I think the problem is on my side. On Fri Nov 14 2014 at 1:05:30 PM 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: On the run rght now, but john merged a patch in that area yesterday, can you try reverting that one? On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com wrote: I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) I'm sure something is wrong locally but I don't see what. Any hint ? 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
Re: [gwt-contrib] Not able to run any GWTTestCase
Deleted all unit caches? On Nov 14, 2014 1:10 PM, Julien Dramaix julien.dram...@gmail.com wrote: I have this problem for several days in fact. It's why I think the problem is on my side. On Fri Nov 14 2014 at 1:05:30 PM 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: On the run rght now, but john merged a patch in that area yesterday, can you try reverting that one? On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com wrote: I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) I'm sure something is wrong locally but I don't see what. Any hint ? 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
Re: [gwt-contrib] Not able to run any GWTTestCase
I've deleted the unit caches and have still the issue. But now that you are talking about unit cache I've seen this line in the log: Could not find the GWT compiler jarfile. Serialization errors might occur when accessing the persistent unit cache. But I've checked my classpath and the gwt jar files (user and dev) are there. Am I missing something for the tests ? On Fri Nov 14 2014 at 1:12:02 PM 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Deleted all unit caches? On Nov 14, 2014 1:10 PM, Julien Dramaix julien.dram...@gmail.com wrote: I have this problem for several days in fact. It's why I think the problem is on my side. On Fri Nov 14 2014 at 1:05:30 PM 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: On the run rght now, but john merged a patch in that area yesterday, can you try reverting that one? On Friday, November 14, 2014, Julien Dramaix julien.dram...@gmail.com wrote: I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at
[gwt-contrib] com.google.web.bindery.autobean.vm.Configuration#setCategories(): unneeded creation of an array list?
Hi,
While trying to find the cause for a very odd NPE I noticed that
Configuration#setCategories() is implemented like this
public Builder setCategories(Class?... categories) {
toReturn.categories =
Collections.unmodifiableList(new
ArrayListClass?(Arrays.asList(categories)));
return this;
}
Could someone explain why there is an explicit creation of the ArrayList
done there? Both the result of Arrays.asList() and a java.util.ArrayList
implement
RandomAccess, so for Collections#unmodifiableList() nothing really should
change there.
Regards,
--
Andreas
--
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/3cf55482-febb-4bf4-8958-664e4aca4055%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: com.google.web.bindery.autobean.vm.Configuration#setCategories(): unneeded creation of an array list?
On Friday, November 14, 2014 1:14:08 PM UTC+1, Andreas Kohn wrote:
Hi,
While trying to find the cause for a very odd NPE I noticed that
Configuration#setCategories() is implemented like this
public Builder setCategories(Class?... categories) {
toReturn.categories =
Collections.unmodifiableList(new
ArrayListClass?(Arrays.asList(categories)));
return this;
}
Could someone explain why there is an explicit creation of the ArrayList
done there? Both the result of Arrays.asList() and a java.util.ArrayList
implement
RandomAccess, so for Collections#unmodifiableList() nothing really should
change there.
This is legal Java:
Class?[] classes = new Classes?[] { foo, bar };
builder.setCategories(classes);
classes[1] = baz;
This explicit copy prevents the builder (actually and more importantly its
toReturn) from being modified from the outside: toReturn.categories is
guaranteed to contain foo and bar, and not baz.
This is a standard pattern. Not doing the copy would actually be flagged as
a possible source of error by things like Checkstyle and/or Findbugs (can't
remember which ones flags this).
--
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/eae2d98d-b20a-4331-9ed0-8dd075895a7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Not able to run any GWTTestCase
This looks awfully a class path issue. Did you ant clean before building? On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix julien.dram...@gmail.com wrote: I've updated my master branch (of the GWT-core project) the with the remote and now I'm not able to run any GWT test cases included in the project. I receive first this error: java.lang.NoSuchFieldError: VOID at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368) at com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601) at com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Then each test case fails with: java.lang.NullPointerException at com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321) at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277) at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671) at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421) at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) I'm sure something is wrong locally but I don't see what. Any hint ? 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%3D66%3DKJkw6JW%3D4Lyk%2BPNkD6z_PMyqQp2zW%3D9ggVTjoVDrA%40mail.gmail.com
