Updated the remaining JVM dependencies from v1.6 to v1.7.
Removed dependencies on the Servlet and JSP API from the Repose-WAR.
Code reformat with no functional changes.
Normalized the element order of the installation POM's.
Replaced the deprecated expression ${artifactId} with the recommended ${project.artifactId}.
Removed CLI-Utils from the installation RPM and Deb POM's.
Normalized the installation POM <name> elements/descriptions and a few comments.
Updated the installation POM's to copy the currently installed artifacts to the current ${project.build.directory} for use in packaging instead of relying on the developer to have executed the build from a higher level.
Fixed the inconsistent/redundant dependency/requires statements in the RPM and Deb POM/control.
Update the instalation RPM Repose-WAR POM to put the ROOT.war in a location consistent with the Linux Filesystem Hierarchy Standard where the local admin can link to it to install Repose into the desired container.
Moved some elements around to facilitate easier comparisons between the standard and Utility Grid flavors of the valve and filters POM's.
Fixed a couple of obvious maintenance oversights on the Utility Grid flavors.
Added a new project to the installation tree for a Debian package of the Repose-WAR.
As per the Product Manager, we nolonger need to create the Utility Grid artifacts.
I did not remove them from the code from the project as per REP-710, but I did want to get the creation of them out of the build.
Added the new Debian Repose-WAR to the modules to be built.
Added two new shell scripts in the installation project, one for RPM and one for Deb.
These are intended to be executed in place and utilize the patch file that was added to the common installation files.
These test scripts:
 - clean and build the respective artifacts
 - copy them to a directory accessible by a Vagrant VM
 - stand up an appropriate Vagrant VM
 - install the artifacts and ancillary packages to run the test
 - execute the test
 - tear down the Vagrant VM
 - leave the test output and current log in the directory that was accessible by the Vagrant VM
There is a not to perform an "rm -Rf Vagrant" in the directory once the examiniation of the out is complete.
Merge pull request #1081 from rackerlabs/REP-889

REP-889 A lot of normalizations in the Installation projects and the addition of the DEB WAR.