date:20160212

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread Michael Zhou

The test still finishes in Eclipse, so when I go to that URL I get an 
ERR_CONNECTION_REFUSED...

On Friday, February 12, 2016 at 4:33:32 PM UTC-5, Daniel Kurka wrote:
>
> If you want to see the console output use a browser to do so, simply pass 
> this in your args:
>
> -Dgwt.args='-runStyle Manual -style PRETTY -setProperty 
> compiler.stackMode=native -port 5454'
>
> Once the test is compiled it will print a url that you can paste into any 
> browser and run the test there. This will also allow you to do debugging 
> directly in that browser
>
>
> On Fri, Feb 12, 2016 at 7:42 PM Michael Zhou  > wrote:
>
>> Hi Daniel,
>>
>> Is there a way to print / log stuff / debug when running a GWTTestCase in 
>> Eclipse? System.out.println() or breakpoints aren't working for me.
>>
>> Michael
>>
>> On Friday, February 12, 2016 at 7:47:38 AM UTC-5, Daniel Kurka wrote:
>>
>>> Hi Michael,
>>>
>>> you are probably missing adding all required source roots to the class 
>>> pathso that the compiler can find the .java .files.
>>>
>>> If you go to your Run Configuration under Classpath, hit adavanced and 
>>> add all required folders 
>>>
>>> At least you should add:
>>>
>>> dev/core/super/
>>> user/src/
>>> user/super/
>>> user/test/
>>> user/test-super/
>>>
>>> Hope that helps,
>>> Daniel
>>>
>>>
>>>
>>>
>>> On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou  
>>> wrote:
>>>
 I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I 
 want to run in Eclipse.
 I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
 When I run the test as a JUnit test, I get:

 com.google.gwt.junit.JUnitFatalLaunchException: The test class 
 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module 
 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was 
 seen
 at 
 com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at junit.framework.TestCase.runBare(TestCase.java:134)
 at junit.framework.TestResult$1.protect(TestResult.java:110)
 at junit.framework.TestResult.runProtected(TestResult.java:128)
 at junit.framework.TestResult.run(TestResult.java:113)
 at junit.framework.TestCase.run(TestCase.java:124)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at junit.framework.TestSuite.runTest(TestSuite.java:243)
 at junit.framework.TestSuite.run(TestSuite.java:238)
 at 
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at 
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
 at 
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
 at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
 at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
 at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
 at 
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

 This seems to happen in any GWTTestCase I tried to run.

 I also see: Could not find the GWT compiler jarfile. Serialization 
 errors might occur when accessing the persistent unit cache.
 from the Eclipse Console.

 -- 
 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/d09b3d03-9111-4109-a735-e33b5c0630a3%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/c851b2a0-f711-407f-8b8e-2b961abc8512%40googlegroups.com
>>  
>>

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread Thomas Broyer

Probably something we should put into a README somewhere ;-)

-- 
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/f8d5c468-d3e4-4b7a-8420-fd6732e8ec25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread 'Daniel Kurka' via GWT Contributors

If you want to see the console output use a browser to do so, simply pass
this in your args:

-Dgwt.args='-runStyle Manual -style PRETTY -setProperty
compiler.stackMode=native -port 5454'

Once the test is compiled it will print a url that you can paste into any
browser and run the test there. This will also allow you to do debugging
directly in that browser


On Fri, Feb 12, 2016 at 7:42 PM Michael Zhou 
wrote:

> Hi Daniel,
>
> Is there a way to print / log stuff / debug when running a GWTTestCase in
> Eclipse? System.out.println() or breakpoints aren't working for me.
>
> Michael
>
> On Friday, February 12, 2016 at 7:47:38 AM UTC-5, Daniel Kurka wrote:
>
>> Hi Michael,
>>
>> you are probably missing adding all required source roots to the class
>> pathso that the compiler can find the .java .files.
>>
>> If you go to your Run Configuration under Classpath, hit adavanced and
>> add all required folders
>>
>> At least you should add:
>>
>> dev/core/super/
>> user/src/
>> user/super/
>> user/test/
>> user/test-super/
>>
>> Hope that helps,
>> Daniel
>>
>>
>>
>>
>> On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou 
>> wrote:
>>
>>> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I
>>> want to run in Eclipse.
>>> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
>>> When I run the test as a JUnit test, I get:
>>>
>>> com.google.gwt.junit.JUnitFatalLaunchException: The test class
>>> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module
>>> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was
>>> seen
>>> at
>>> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
>>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
>>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
>>> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
>>> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
>>> at junit.framework.TestCase.runBare(TestCase.java:134)
>>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>>> at junit.framework.TestResult.run(TestResult.java:113)
>>> at junit.framework.TestCase.run(TestCase.java:124)
>>> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
>>> at junit.framework.TestSuite.runTest(TestSuite.java:243)
>>> at junit.framework.TestSuite.run(TestSuite.java:238)
>>> at
>>> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>>>
>>> This seems to happen in any GWTTestCase I tried to run.
>>>
>>> I also see: Could not find the GWT compiler jarfile. Serialization
>>> errors might occur when accessing the persistent unit cache.
>>> from the Eclipse Console.
>>>
>>> --
>>> 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/d09b3d03-9111-4109-a735-e33b5c0630a3%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/c851b2a0-f711-407f-8b8e-2b961abc8512%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 th

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread Michael Zhou

Hi Daniel,

Is there a way to print / log stuff / debug when running a GWTTestCase in 
Eclipse? System.out.println() or breakpoints aren't working for me.

Michael

On Friday, February 12, 2016 at 7:47:38 AM UTC-5, Daniel Kurka wrote:
>
> Hi Michael,
>
> you are probably missing adding all required source roots to the class 
> pathso that the compiler can find the .java .files.
>
> If you go to your Run Configuration under Classpath, hit adavanced and add 
> all required folders 
>
> At least you should add:
>
> dev/core/super/
> user/src/
> user/super/
> user/test/
> user/test-super/
>
> Hope that helps,
> Daniel
>
>
>
>
> On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou  > wrote:
>
>> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I 
>> want to run in Eclipse.
>> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
>> When I run the test as a JUnit test, I get:
>>
>> com.google.gwt.junit.JUnitFatalLaunchException: The test class 
>> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module 
>> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was 
>> seen
>> at 
>> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
>> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
>> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
>> at junit.framework.TestCase.runBare(TestCase.java:134)
>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>> at junit.framework.TestResult.run(TestResult.java:113)
>> at junit.framework.TestCase.run(TestCase.java:124)
>> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
>> at junit.framework.TestSuite.runTest(TestSuite.java:243)
>> at junit.framework.TestSuite.run(TestSuite.java:238)
>> at 
>> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>> at 
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>> at 
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>>
>> This seems to happen in any GWTTestCase I tried to run.
>>
>> I also see: Could not find the GWT compiler jarfile. Serialization errors 
>> might occur when accessing the persistent unit cache.
>> from the Eclipse Console.
>>
>> -- 
>> 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/d09b3d03-9111-4109-a735-e33b5c0630a3%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/c851b2a0-f711-407f-8b8e-2b961abc8512%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Compiler failing with java 7

2016-02-12 Thread Brandon Donnelson

I would choose Java 1.8 all the way if you have to choose. I would do this 
because this is going to be a long standing maintenance release. Just a 
note, the Eclipse neon out in June will require Java 1.8. I think it makes 
sense to upgrade. I think folks can go through the pain of upgrading there 
servlet containers to Java 1.8 if they want to move forward. 


On Friday, February 12, 2016 at 8:39:41 AM UTC-8, Colin Alworth wrote:
>
> Switching to gwt-contrib, we're losing voices who are involved in this 
> discussion. 
>
> Maybe I am missing something, but I had that that the discussion moved 
> toward the fact that the compiler and dev mode will require Java8, but that 
> gwt-servlet could still be compiled to Java7, allowing deployment on Java7. 
>
> The supersource classes do require Java8 language level in the GWT 
> compiler (in order to have "default" mean anything), but these emulation 
> classes are not compiled to bytecode, and not required to compile the rest 
> of GWT. 
>
> We already have cases where GWT will not work without Java8 (specifically 
> Dev Mode and anything that leans on it), so this isn't a change from the 
> beta. I agree with Daniel that effort will be required to compile to Java7 
> bytecode (as previously discussed), and while I would be interested in 
> helping to achieve this, we've also clearly stated that Java8 support is a 
> more important goal (both in terms of keeping GWT modern and up to date in 
> the Java world, but also in terms of staying relevant for web development 
> with lambdas and JSInterop).
>
> Even if we manage to compile to Java7 bytecode from a Java8 JDK, it has 
> been encouraged that we extensively test to ensure that all of the code 
> does as we expect, as regressions have been seen in the past. RetroLambda 
> was another suggestion that also may have merit.
>
> On Fri, Feb 12, 2016 at 10:28 AM Daniel Kurka  > wrote:
>
>> GWT 2.8 needs to contain Java8 APIs so taht guava will start working 
>> again. All the outstanding Java8 patches need to go in before 2.8. So 2.8 
>> will not work with Java7.
>>
>>
>> On Fri, Feb 12, 2016 at 5:25 PM Jens Nehlmeier > > wrote:
>>
>>> Its not just about adding new classes but we also add APIs to existing
>>> classes that require Java8 classes in their signature. So you would
>>> need to ignore these changes on method level.
>>>
>>> AFAICT it was said that as soon as Java 8 APIs are committed GWT will
>>> require Java8. If someone needs Java7 support they need to replace the
>>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>>> is something to think about as soon as we want to add GWT-RPC
>>> serializer for Java 8 classes. If we really want to give users the
>>> possibility to compile GWT 2.8 with Java 7 after replacing the
>>> emulation code we probably need a build target that builds
>>> gwt-servlet-jdk8.jar when running Java8 only.
>>>
>>> Generally I thought Java8 stuff will be committed after GWT 2.8 has
>>> been released so that GWT 2.8 stays Java7 compatible. I don't know
>>> about the Guava issue that requires GWT 2.8 to already have Java8 APIs
>>> available. I thought Guava will just release Guava 20 when 2.8 is
>>> released because Gauva 19 did use some private APIs of GWT that do not
>>> exist anymore.
>>>
>>>
>>>
>>> 2016-02-12 16:06 GMT+01:00 Daniel Kurka >> >:
>>> > +Colin Alworth  +Jens
>>> >
>>> > Colin and Jens have been doing a lot of the Java8 API work, I believe 
>>> this
>>> > will touch many classes within the JRE and thus will not be as easy as
>>> > ignoring a few classes.
>>> >
>>> > To be clear:
>>> > We won't be putting any resources into addressing this since its not an
>>> > issue for us, if someone feels strongly (s)he can step up and tackle 
>>> this,
>>> > but the whole case does not seem to be convincing for me, why would 
>>> agencies
>>> > that are slow to adopt things adopt the latest GWT version?
>>> >
>>> > -Daniel
>>> >
>>> > On Fri, Feb 12, 2016 at 3:52 PM Manuel Carrasco Moñino <
>>> man...@apache.org >
>>> > wrote:
>>> >>
>>> >> Well the situation I know, is that there are many big companies and
>>> >> government agencies moving very slow, their standard server 
>>> configuration is
>>> >> java7, as well as their code standards.
>>> >>
>>> >> Their GWT projects are compiled in one phase (not client and server
>>> >> sides). It could be very difficult for them to compile their byte 
>>> code for
>>> >> 1.7.
>>> >> It's true that if they don't use java 8 many features in 2.8 are 
>>> useless
>>> >> for them, but we have to facilitate and encourage users to be in 
>>> latest
>>> >> version.
>>> >>
>>> >> I don't know how complex it could be, but if for example, ignoring 
>>> java8
>>> >> /emul/ classes could fix the problem I think it's worth to consider.
>>> >>
>>> >> On Fri, Feb 12, 2016 at 3:42 PM, 'Daniel Kurka' via gwt-maintainers
>>> >> > wrote:
>>> >>>
>>> >>> I am not sure ho

[gwt-contrib] Re: Compiler failing with java 7

2016-02-12 Thread Colin Alworth

Switching to gwt-contrib, we're losing voices who are involved in this
discussion.

Maybe I am missing something, but I had that that the discussion moved
toward the fact that the compiler and dev mode will require Java8, but that
gwt-servlet could still be compiled to Java7, allowing deployment on Java7.

The supersource classes do require Java8 language level in the GWT compiler
(in order to have "default" mean anything), but these emulation classes are
not compiled to bytecode, and not required to compile the rest of GWT.

We already have cases where GWT will not work without Java8 (specifically
Dev Mode and anything that leans on it), so this isn't a change from the
beta. I agree with Daniel that effort will be required to compile to Java7
bytecode (as previously discussed), and while I would be interested in
helping to achieve this, we've also clearly stated that Java8 support is a
more important goal (both in terms of keeping GWT modern and up to date in
the Java world, but also in terms of staying relevant for web development
with lambdas and JSInterop).

Even if we manage to compile to Java7 bytecode from a Java8 JDK, it has
been encouraged that we extensively test to ensure that all of the code
does as we expect, as regressions have been seen in the past. RetroLambda
was another suggestion that also may have merit.

On Fri, Feb 12, 2016 at 10:28 AM Daniel Kurka  wrote:

> GWT 2.8 needs to contain Java8 APIs so taht guava will start working
> again. All the outstanding Java8 patches need to go in before 2.8. So 2.8
> will not work with Java7.
>
>
> On Fri, Feb 12, 2016 at 5:25 PM Jens Nehlmeier 
> wrote:
>
>> Its not just about adding new classes but we also add APIs to existing
>> classes that require Java8 classes in their signature. So you would
>> need to ignore these changes on method level.
>>
>> AFAICT it was said that as soon as Java 8 APIs are committed GWT will
>> require Java8. If someone needs Java7 support they need to replace the
>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this
>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar
>> is something to think about as soon as we want to add GWT-RPC
>> serializer for Java 8 classes. If we really want to give users the
>> possibility to compile GWT 2.8 with Java 7 after replacing the
>> emulation code we probably need a build target that builds
>> gwt-servlet-jdk8.jar when running Java8 only.
>>
>> Generally I thought Java8 stuff will be committed after GWT 2.8 has
>> been released so that GWT 2.8 stays Java7 compatible. I don't know
>> about the Guava issue that requires GWT 2.8 to already have Java8 APIs
>> available. I thought Guava will just release Guava 20 when 2.8 is
>> released because Gauva 19 did use some private APIs of GWT that do not
>> exist anymore.
>>
>>
>>
>> 2016-02-12 16:06 GMT+01:00 Daniel Kurka :
>> > +Colin Alworth  +Jens
>> >
>> > Colin and Jens have been doing a lot of the Java8 API work, I believe
>> this
>> > will touch many classes within the JRE and thus will not be as easy as
>> > ignoring a few classes.
>> >
>> > To be clear:
>> > We won't be putting any resources into addressing this since its not an
>> > issue for us, if someone feels strongly (s)he can step up and tackle
>> this,
>> > but the whole case does not seem to be convincing for me, why would
>> agencies
>> > that are slow to adopt things adopt the latest GWT version?
>> >
>> > -Daniel
>> >
>> > On Fri, Feb 12, 2016 at 3:52 PM Manuel Carrasco Moñino <
>> man...@apache.org>
>> > wrote:
>> >>
>> >> Well the situation I know, is that there are many big companies and
>> >> government agencies moving very slow, their standard server
>> configuration is
>> >> java7, as well as their code standards.
>> >>
>> >> Their GWT projects are compiled in one phase (not client and server
>> >> sides). It could be very difficult for them to compile their byte code
>> for
>> >> 1.7.
>> >> It's true that if they don't use java 8 many features in 2.8 are
>> useless
>> >> for them, but we have to facilitate and encourage users to be in latest
>> >> version.
>> >>
>> >> I don't know how complex it could be, but if for example, ignoring
>> java8
>> >> /emul/ classes could fix the problem I think it's worth to consider.
>> >>
>> >> On Fri, Feb 12, 2016 at 3:42 PM, 'Daniel Kurka' via gwt-maintainers
>> >>  wrote:
>> >>>
>> >>> I am not sure how this is connected to the beta1 release. Beta1 did
>> not
>> >>> have any Java8 apis for the final release we need them to support the
>> next
>> >>> version of guava.
>> >>>
>> >>> If you feel strongly you can always step in with a design that will
>> >>> support both modes and execute on it, but we went over this in the SC
>> and
>> >>> this seems like a lot of work for something that almost all devs are
>> fine
>> >>> with (run java8 while developing).
>> >>>
>> >>>
>> >>> On Fri, Feb 12, 2016 at 3:36 PM Manuel Carrasco Moñino
>> >>>  wrote:
>> 
>>  Since beta1 supports 1.7, isn't feas

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread Michael Zhou

Thanks Daniel, adding

gwt-dev/core/super/
gwt-user/core/src/
gwt-user/core/super
gwt-user/code/test 

works.

Michael

On Friday, February 12, 2016 at 7:47:38 AM UTC-5, Daniel Kurka wrote:
>
> Hi Michael,
>
> you are probably missing adding all required source roots to the class 
> pathso that the compiler can find the .java .files.
>
> If you go to your Run Configuration under Classpath, hit adavanced and add 
> all required folders 
>
> At least you should add:
>
> dev/core/super/
> user/src/
> user/super/
> user/test/
> user/test-super/
>
> Hope that helps,
> Daniel
>
>
>
>
> On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou  > wrote:
>
>> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I 
>> want to run in Eclipse.
>> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
>> When I run the test as a JUnit test, I get:
>>
>> com.google.gwt.junit.JUnitFatalLaunchException: The test class 
>> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module 
>> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was 
>> seen
>> at 
>> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
>> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
>> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
>> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
>> at junit.framework.TestCase.runBare(TestCase.java:134)
>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>> at junit.framework.TestResult.run(TestResult.java:113)
>> at junit.framework.TestCase.run(TestCase.java:124)
>> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
>> at junit.framework.TestSuite.runTest(TestSuite.java:243)
>> at junit.framework.TestSuite.run(TestSuite.java:238)
>> at 
>> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>> at 
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>> at 
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>> at 
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>>
>> This seems to happen in any GWTTestCase I tried to run.
>>
>> I also see: Could not find the GWT compiler jarfile. Serialization errors 
>> might occur when accessing the persistent unit cache.
>> from the Eclipse Console.
>>
>> -- 
>> 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/d09b3d03-9111-4109-a735-e33b5c0630a3%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/0c0fea4f-c43a-4428-a948-f01874aa8c05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread 'Daniel Kurka' via GWT Contributors

Hi Michael,

you are probably missing adding all required source roots to the class
pathso that the compiler can find the .java .files.

If you go to your Run Configuration under Classpath, hit adavanced and add
all required folders

At least you should add:

dev/core/super/
user/src/
user/super/
user/test/
user/test-super/

Hope that helps,
Daniel




On Fri, Feb 12, 2016 at 12:02 PM Michael Zhou 
wrote:

> I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I
> want to run in Eclipse.
> I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
> When I run the test as a JUnit test, I get:
>
> com.google.gwt.junit.JUnitFatalLaunchException: The test class
> 'com.google.gwt.emultest.java.util.BitSetTest' was not found in module
> 'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was
> seen
> at
> com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
>
> This seems to happen in any GWTTestCase I tried to run.
>
> I also see: Could not find the GWT compiler jarfile. Serialization errors
> might occur when accessing the persistent unit cache.
> from the Eclipse Console.
>
> --
> 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/d09b3d03-9111-4109-a735-e33b5c0630a3%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/CALLujipHqbc7jLOp77vH2w2go1wGH8_khSXSgLchSV0OwSFi6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Not able to run GWTTestCase in Eclipse

2016-02-12 Thread Michael Zhou

I have a test under gwt-user/core/test/com/google/gwt/emultest/ that I want 
to run in Eclipse.
I imported gwt-user and gwt-dev according to trunk/eclipse/README.md.
When I run the test as a JUnit test, I get:

com.google.gwt.junit.JUnitFatalLaunchException: The test class 
'com.google.gwt.emultest.java.util.BitSetTest' was not found in module 
'com.google.gwt.emultest.EmulSuite'; no compilation unit for that type was 
seen
at 
com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:734)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1327)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1283)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

This seems to happen in any GWTTestCase I tried to run.

I also see: Could not find the GWT compiler jarfile. Serialization errors 
might occur when accessing the persistent unit cache.
from the Eclipse Console.

-- 
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/d09b3d03-9111-4109-a735-e33b5c0630a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

[gwt-contrib] Re: Compiler failing with java 7

[gwt-contrib] Re: Compiler failing with java 7

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

Re: [gwt-contrib] Not able to run GWTTestCase in Eclipse

[gwt-contrib] Not able to run GWTTestCase in Eclipse

9 matches

Site Navigation

Mail list logo

Footer information