-
1. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
csa Jul 15, 2013 6:21 AM (in response to magick93)Hi Anton,
Starting with Errai 2.3 we upgraded to GWT 2.5. You need to upgrade the gwt and gwt.maven versions to 2.5.1. I assume your build will work after that.
There seems to be classpath scanning issue though that we need to look into.
Cheers,
Christian
-
2. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
magick93 Jul 16, 2013 9:08 AM (in response to csa)HI Christian
I have upgraded to GWT 2.5.1, and am still getting the same errors.
I have attached the output again.
Any advice on how to proceed is greatly appreciated.
-
3. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
csa Jul 16, 2013 10:48 AM (in response to magick93)Hi Anton,
Looking at your log, you now have both gwt 2.4.0 and 2.5.1 on the classpath. The gwt maven plugin is also still 2.4.0.
You could run mvn dependency:tree to see where the GWT 2.4.0 dependency comes from.
Cheers,
Christian
-
4. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
magick93 Jul 17, 2013 11:48 AM (in response to csa)Thanks Christian
That did it.
-
5. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
calca Jul 17, 2013 8:32 PM (in response to magick93)Hey Guys, after migrating our app to Erray 2.4 beta1, it compiles and run locally, but for some reason in jenkins hangs. The last line logged we can see is the following:
"Checking ErraiApp.properties for configured types ..."
and then it just hangs there and never finishes. Do you have some idea of what could be causing it, or what should we check?
Thanks!
Demian
-
6. Re: Failed attempt to upgrade to 2.4 beta 1 - strange console errors
csa Jul 19, 2013 10:57 AM (in response to calca)Hi Demian,
You can try giving the build more heap space e.g. try with -Dgwt.extraJvmArgs="-Xmx1024m".
If that doesn't do it, please start a new thread as this one is resolved and somewhat unrelated.
Cheers,
Christian