Neils Info 2: 2014

Just had fun dealing with an error when deploying to appengine that said that I need to compile my module. After much searching and playing, I finally discovered that I had to run a maven compile first. I had been avoiding that because my maven compiles had been erroring out. I assumed that they weren't doing anything. They were apparently doing enough, though, to allow the google eclipse plugin to finish the job when deploying.

Upon investigation of the compile error I discovered that the default pom.xml that is created by gwt-maven-plugin had the scope for the validation-api dependency set to test. Setting it to provided solved the problem. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html for more information on scope.

<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<classifier>sources</classifier>
<scope>provided</scope>
</dependency>

Getting GWT and AppEngine working together using Maven

Turns out that the gwt-maven-plugin does most of the work for you as long as you are using eclipse and the eclipse google plugin. The server configuration setting in the POM.xml does everything that you need. See the POM.xml snippet below.

Here are a couple of gotchas:

You need to use the eclipse plugin to turn on appengine support.
You'll need to create an appengine-web.xml

Note that when I tried deploying to appengine even though my app_id was correct in the appengine-web.xml file I would get an error saying that the app didn't exist on appengine and the details showed that it was using the wrong app_id. I couldn't find where eclipse was getting the incorrect app_id from so eventually just deleted all of the eclipse stuff (mvn eclipse:clean) and reimported.

You'll have to adjust your build path and move the maven dependencies to the bottom of the "order and export" list. Otherwise eclipse complains that the appengine-sdk.jar is not a directory.
When I reimported my project into eclipse for some reason the target/generated_sources directory was no longer in the java build path. Add that back in if you get errors about the _async classes not being found.
I had to use eclipse-ee in order to import the maven project properly because it seems like m2e-wtp is required. I wound up installing the latest version of m2e after getting errors about maven, but that was back when I was trying to run the whole project as a maven project using (appenging:devserver). I never did get that method of doing this working. It seems that if you are going to sue the gwt-maven-plugin, you can't combine it with the appengine-maven-plugin.

<groupId>org.codehaus.mojo</groupId>

<artifactId>gwt-maven-plugin</artifactId>

<goals>

<goal>compile</goal>

<goal>generateAsync</goal>

</goals>

</execution>

</executions>

<!-- Plugin configuration. There are many available options, see gwt-maven-plugin

documentation at codehaus.org -->

<extraJvmArgs>-Xss1024K -Xmx1024M -XX:MaxPermSize=256M</extraJvmArgs>

<hostedWebapp>${webappDirectory}</hostedWebapp>

<runTarget>gwtmodule.html</runTarget>

<webappDirectory>${webappDirectory}</webappDirectory>

<server>com.google.appengine.tools.development.gwt.AppEngineLauncher</server>

<i18nMessagesBundle>com.corecompetency.gwt.client.Messages</i18nMessagesBundle>

<appEngineVersion>${appengine.target.version}</appEngineVersion>

<compileReport>false</compileReport>

</configuration>

</plugin>

Friday, July 11, 2014

Can i use the google app engine eclipse plugin with a maven gae project? - Stack Overflow

Can i use the google app engine eclipse plugin with a maven gae project? - Stack Overflow:

'via Blog this'

Thursday, July 10, 2014

Up and Running on AppEngine With Maven, Jersey and Guice - Part 3 - Akshay's Programming Blog

Up and Running on AppEngine With Maven, Jersey and Guice - Part 3 - Akshay's Programming Blog:

'via Blog this'

Monday, July 7, 2014

google app engine - GWT + Appengine + JPA + Eclipse + Maven: How to get them to work together - Stack Overflow

google app engine - GWT + Appengine + JPA + Eclipse + Maven: How to get them to work together - Stack Overflow:

'via Blog this'

Sunday, July 6, 2014

Structuring GWT modules for large applications | Summa Blog

Structuring GWT modules for large applications | Summa Blog:

'via Blog this'

Wednesday, June 18, 2014

Version of Linux on nexus 7

http://forum.xda-developers.com/showthread.php?t=2577356

Sunday, June 15, 2014

GWT helpers

Demystifying MVP
GWT Event Binder
GWTMockito for unit testing when using composite classes instead of presenter/view

Saturday, June 14, 2014

GWT and guice example

http://www.canoo.com/blog/2011/04/05/gwt-dependency-injection-recipes-using-gin/

Monday, June 2, 2014

Latest package of freenect for armel

https://launchpad.net/ubuntu/quantal/armel/freenect/1:0.1.2+dfsg-6

Saturday, May 31, 2014

Xtion Kinect alternative

http://www.newegg.com/Product/Product.aspx?Item=N82E16826785030

Kinect depth projection to real world coordinates

FovH = 1.0144686707507438 (rad) // horizontal field of view FovV = 0.78980943449644714 (rad) // vertical field of view From there you can find the real world coordinates from the depth cloud like so: // X_proj = X pixel number, Y_proj = Y pixel number // Xres = X resolution (640 for Kinect and Xtion, optional 320 for Xtion // Yres = Y resolution (480 for Kinect and Xtion, optional 240 for Xtion X_rw = (X_proj/Xres-.5) * Z * XtoZ Y_rw = (0.5-Y_proj/Yres) * Z * YtoZ, Z_rw = Z where XtoZ = tan(FovH/2)*2, and YtoZ = tan(FovV/2)*2, and Z is the value given by the depth map at each pixel.