Some labels in the user interface were in Spanish and some in English.
This commit standardizes the language used to Spanish, translating every
label to that language.

Database encoding has been changed to UTF-8. This should solve character
presentation errors in Windows environments.

The command to execute the application launching it without watching the
file system was not currently working, as the command used "cargo:start"
closed Tomcat when the construction finished.

This command has been replaced by "cargo:run", that blocks the
construction avoiding Tomcat shut down.

The name of the Gecko driver was incorrect for Windows 32 bit
architectures, as the prefix used was "win86" instead of "win32".

In addition, the Gecko driver storage path into maven local repository
has been simplified.

Red background was added to the body of the login view for debugging
purposes, but shouldn't have passed to a stable release. This commit
removes the red background configuration.

The application appearance has been improved applying Bootstrap formats.

The dependencies version has been updated in the POM file to the latest
versions. In addition, the POM file format has been unified.

Some "console.logs" have been removed from the PeopleView class and the full
resposibility for the edition and deletion of people has been moved to public
methods of PeopleView.

The execution sections of the README.md now include a link to the application
home when it is started using the provided commands.

The frontend has been refactorized to use classes in the JavaScript files.

Some backend classes have been refactorized and simplified.

The EqualsVerifier library has been added to test the equals and hashCode
methods and it has been used to test the Person entity.

This commit updates the README.md file to include better and more detailed
descriptions of how to construct and execute the application.

The run-tomcat-mysql allows the execution of the project in a Tomcat 8 server
with a MySQL database through the "cargo:run" or "cargo:start" goals. This
commit adds the fizzed-watcher-maven-plugin to provide the project with
automatic redeployment when using the aforementioned profile.

For example, executing the Maven command the application will be served in a
Tomcat server an automatically redeployed when any file changes:

mvn -DskipTest=true -Prun-tomcat-mysql cargo:start fizzed-watcher:run

This commit updates the dependency and plugin versions in the POM file.
The most important update is the one relative to Selenium, as recent
Firefox browsers do not work with old Selenium Firefox drivers. Now,
during the construction, the Gecko driver is downloaded to work with
recent Firefox browsers.

The login token was incorrectly set to "admin:admin" instead of
"admin:adminpass". This commit fixes this and sets the valid token
value.

The WebContent directory was not used in this project.

The execution command recommended in README.md has been simplified (no tests are executed now) and made more robust by includen a project cleaning and packaging previous to execution.

The POM file has been changed to include the generation of reports for integration tests (execution and coverage) even when acceptance tests are not run.

The Tomcat URL has been changed for a more stable FTP location.

This commit adds the new resource UsersResource (/users) with a simple
functionality: retrieving the data of an user. This functionality
requires knowing the login of the user that is performing the request.
In this regard, this commit is an example of how this information can be
retrieved and how to test a resource that requires knowing the login of
an user.

This test was unintentionally leaved out when creating the test case.

The redirect created in the LoginFilter when the request URL included
query parameters was incomplete, as it missed the "?" that separates the
query parameters from the request URL. This commit fixes this error.

Some columns of the MySQL database created by the scripts in the "db"
directory where incorrectly set as nullable. This commit fixes this
error and sets them as non nullable columns.

The POM has been updated to fix UTF-8 as the source code encoding. This
avoids problems when building the project in Windows systems.

When a user is correctly logged in, the LoginFilter adds the user login
to the HTTP session. This allows, for example, the REST layer to
retrieve the current logged user.

The tests classes have been simplified by delegating some of the
functions in the test classes to external utility classes. For example,
a PeopleDataset has been added to manage the dataset or the
IsEqualToEntity Hamcrest matcher has been added to simplify entity
comparisons.

In addition, a PersonUnitTest class has been added to test the Person
entity.

A big refactorization has been done in this commit, focused on
simplifying the testing and execution process. The Spring-DbUnit library
has been added to allow the use of DbUnit through annotations in the
test classes. This change has been complemented with two new test
listeners that allow the creation of custom initial contexts and the use
of custom SQL scripts to create and destroy the database tables before
and after the test execution, respectively. In addition, all the tests
are executed now using a HSQLDB database.

The datasource configuration has been pulled out of the project, and now
it must be provided by the container.

The sample classes have been reviewed, refactorized and documented with
JavaDoc.

The POM file has been reworked to ease test and application execution
using maven. The new execution modes are:
	- The default execution includes unit, integration and acceptance (with
Selenium) test execution.
	- No acceptance tests: mvn -P -acceptance-tests-cargo <phase>
	- Run server for manual acceptance tests: mvn
-Dcargo.tomcat.start.skip=true -Dcargo.tomcat.run.skip=false
-DskipTests=true pre-integration-test 
	- Run server with MySQL database: mvn -P
run-tomcat-mysql,-acceptance-tests-cargo -DskipTests=true package
cargo:run

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. 

The libraries jersey-test-framework-provider-grizzly2 and commons-dbcp
are only used in the test, but they had the default scope. Now, they are
test scoped.

Dependency with Apache Commons Codec was removed and now the native Java
8 utilities for SHA-256 and Base64 encoding and decoding is used.

The java.util.logging.Logger was introduced as the logger for the
application.

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.

PeopleDAO functions now throw an IllegalArgumentException when an
invalid id or a null name or surname are provided. People's REST API
modified to return a "Bad Request" status when an
IllegalArgumentException is catched.