The performance of the auto-redeploy executions configured in Maven have
been improved by adjusting the directories watched by the plugin
responsible for the redeployment.

The POM and other configuration files have been updated to support a new
execution mode where Cargo is used to execute the backend and NPM to
execute the frontend, both in auto-redeploy mode.

Acceptance tests were not working as they wasn't adapted to the Angular
framework after the migration. This commit fixes these test that now
work again.

The auto-redeploy mode now ignores node_modules, as it slows excesively
down the execution.

The example done for JavaScript, were people can be managed, has been
migrated to Angular.

The version has been changed to start the development of a new
version.

The user authentication was currently done using a cookie and following
the same style of token as the HTTP Basic authentication (i.e. a
concatenation of user and password joined with a ':' encoded with
base64).

This authentication has been replaced by a standard HTTP Basic
authentication.

The message showed currently by the HasHttpStatus when de expected
status didn't match the actual status was not very informative, as
the actual status was not shown in the message.

This commit modifies this behaviour to show both status (expected and
actual) in the message.

The name of the Gecko driver was incorrect for MacOS systems, as the
prefix used was "mac" instead of "macos". This commit changes the prefix
to solve this problem.

Thanks to Ivan Ferrant (iferrant) for this fix.

When an invalid login is provided to the UsersDAO.get method it throws
an IllegalArgumentException. This may happen when the user's credentials
are checked by the LoginFilter, and the exception was not currently
managed. As a result, an user trying to login with an invalid login will
access the main.html page showing an error message.

This commit fixes this error, and invalid user login attempts now return
to the index.html page.

Commit 9ef1c405 redesigned the user interface by introducing Bootstrap.
Although the structure changes where minimal, the changes on class types
caused the page object classes' selectors to fail.

This commit fixes this error and, in addition, fixes an unexpected error
on person deletion. This error was caused due to a missing wait for an
AJAX request response.

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 dependencies version has been updated in the POM file to the latest
versions. In addition, the POM file format has been unified.

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

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 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.

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

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

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.

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.

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.

Access to any resource except index.html can be restricted enabling the
LoginFilter in the web.xml configuration file. It is currently disabled.

Old index.html moved to main.html and replaced with an index.html that
contains a login form.

In this first version, this applicacion includes a complete CRUD using
an AJAX+JSON+REST architecture.