Brandon ref5 multiproject mavenize gwt tests2

This adds in some testing, although I'm having problems with the local datastore config for some reason. I'm probably missing something simple. 

But the real issue that bugs me is the Ref<?> is easy to get from client. But when saving from client, its a pain, b/c it requires some funky logic. I've been wondering, why do I need a key value map for a relationship when the owned object could store the key. Maybe its b/c the @Id is Long and doesn't store the entire value of the app engine key. I think @Id could be a objectify.Key<?> storing the value needed and then no special logic would be needed in the domain object. But this would require some core changes and input from Jeff and community. So keeping ref will require a little core change so the object is bidirectional persay, so it can get and put with out much thought. Anyway those are my thoughts on this so far. 

GWT seems to handle custom serialization just fine. Although it creates a more custom setup and debugging. This module is nice for debugging gwt with out having to compile a objectify lib. And with maven its a simple maven project import into eclipse.