While paving the way to ValueStore, I've greatly simplified
EntityRefs. They are now singletons, and I've resumed referring to
them as Keys, since that's really how they act. This means that a
RequestFactory based app really won't have to any instantiation of its
DTOs beyond calling eval().

They keys also now instance based, and provide accessors to get to
their properties. The result is a lot less reflection code server
side.

I haven't yet done checkstyle fixes, just want to get this up where it
can be looked at.

Review at http://gwt-code-reviews.appspot.com/243801

Review by: amitmanjhi@google.com

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@7750 8db76d5a-ed1c-0410-87a9-c151d255dfc7

bikeshed/eclipse.README

diff --git a/bikeshed/eclipse.README b/bikeshed/eclipse.README
index be52ce2..4bcdab2 100644
--- a/bikeshed/eclipse.README
+++ b/bikeshed/eclipse.README
@@ -13,8 +13,10 @@
 # Matches gwtc output in the war directory, e.g. war/com.google.gwt.bikeshed.tree.Tree/
 com.google.gwt.*
 bikeshed/war/expenses/
+bikeshed/war/expensesScaffold/
 bikeshed/war/stocks/
 bikeshed/war/tree/
+bikeshed/war/validation/
 
 * Install the Google Plugin for Eclipse
 * Import trunk/bikeshed/ as a new Java project with existing source