DatabaseQueryUnitTest mocks the database and there is no need to create
a testing database. Therefore, the TestUtils method calls to initialize
and clear the testing database where removed.

Several testing improvement have been done:
	- Cobertura plugin was replaced by JaCoCo plugin that supports Java 8
syntax.
	- Unit tests with a controller fixtured using EasyMock were added for
PeopleDAO and PeopleResource.
	- POM was reviewed, reordered and reformatted.
	- Test classes naming was reviewed and standarized.
	- Three test suites were added to group the unit, integration, and
acceptance tests.
	- Naming context management done in TestUtils was improved. 

Web configuration for REST services and login filter was moved from the
web.xml file to code annotations.

POM was reviewed to update the dependencies of the project to the last
version and to improve the test execution.

Now it is possible to run the project with the testing database in a
Tomcat Server v7.0 using the mvn tomcat7:run goal. In addition, Selenium
tests now are executed as integration tests, starting the web server
before the test execution and stoping it after the tests end. Finally,
support for generating regular and cobertura test reports in HTML format
was also added.

The project was also cleaned by removing the MANIFEST.MF files and by
reallocating the SQL files.

Sunfire report generation plugin added to pom.xml.

Minor code cleaning in pom.xml and PeopleWebTest class.

New login method based in HTTP's Basic Authentication used. This new
method eliminates the need of the database supporting the SHA256
algorithm and facilitates the future use of Basic Authentication.

Tests were updated to use the new token encoding.

DAO class modified to support and alternative JNDI for the data source
through the "db.jndi" system property. A new testing database resource
was added to the Context.xml file.

DAO tests use the "spring-test" library to create a JNDI context, as
JUnit doesn't create any context. Additionaly, a custom DataSource is
created using the "commons-dbcp" library and injected into the context.
Testing database creation scripts are provided in the mysql-tests.sql
file.

REST API is tested in the server side using the
"jersey-test-framework-provider-grizzly2" library. These tests also use
the "spring-test" and "commons-dbcp" libraries to create a context and
inject a custom data source.

REST API is tested in the client side using the "Selenium IDE" and
"RESTClient" plugins for Firefox. Manual database reset is required
before launching the test suite.

Web interface is tested using the "Selenium IDE" plugin for Firefox and
using the "Selenium WebDrive" in JUnit tests. Same tests are implemented
in both cases. Selenium IDE tests require a manual database reset before
launching the test suite. JUnit test require the server to be started
using the testing database.