Generalizing some build settings in the parent pom to avoid some repitition in modules - also fixes encoding issues on some systems
Brought the Core gwt module out into its own maven module to allow it to be depended on by both -dev and -user. Added additional dependencies to enable both sources and tests in -core, -dev, and -user to compile cleanly (with two minor generics fixes in -user). Started to bring in sources essential to GWT to compile to JS, but need to step carefully around bringing in too much to see if a src/main/lang would be handy to have.
Deleted what look like text editor backup files
Moved gwt lang code back into src/main/java for now in the -dev project, subject to future breakup
Renaming groupId to com.google.gwt as it is known in the maven world today, and removing unnecessary tags in sub-project poms
Switching to public htmlunit release and modifying resources to that tests seem to build and start passing in -user (not dev yet) - getting close to the point where projects can build with this.
Removed -user-super, merging it back into -user so that tests can find those classes correctly. Also restored packages so that modules can selectively pull in some sub-packages as super source, but not others.
Adding missing super sources to make java translatable, as well as several other super'd packages
modified maven-gwt-compiler pom details in -{parent,user}

[INFO] gwt-parent ........................................ SUCCESS [0.360s]
[INFO] gwt-core .......................................... SUCCESS [2.614s]
[INFO] gwt-dev_core ...................................... SUCCESS [18.305s]
[INFO] gwt-user .......................................... SUCCESS [51.017s]
[INFO] gwt-build_tools_ant_gwt ........................... SUCCESS [1.707s]
[INFO] gwt-build_tools_doctool ........................... FAILURE [1.336s]