The wildfly-mysql-run profile has been improved by changing the wildfly
goal added to the install phase to deploy-only instead of deploy. This
should reduce the startup time.

The default FirefoxDriver from Selenium no longer supports Firefox since
version 47 without a native web driver. This commit adds support to
native drivers, downloading and configuring this drivers depending on
the current OS (only Unix, Windows and Mac OS supported at this moment).

The previous Maven configuration included a WildFly Maven plugin
configuration in the H2 and MySQL profiles that allowed the application
execution directly from Maven (with the mvn wildfly:start wildfly:deploy
command). As this configuration included a custom WildFly deployment
configuration (that modified the standalone.xml of the WildFly where the
application will be deployed), the mvn wildfly:deploy couldn't be used
to deploy the application in a local WildFly instance.

This commit adds a new profile (wildfly-mysql-run) that can be used to
execute the application directly from Maven (with the mvn install
command). The custom WildFly plugin configuration has been removed from
the other profiles, allowing users to normally deploy the application in
a running WildFly instances.

Instructions on how to use the profiles for application execution and
deployment can be found in the README.md file.

The project configuration has been simplified by unifying some part of
the mysql and h2 configurations.

In addition, the project has been configured to allow the execution of
the application with the Maven WildFly plugin.

The README.md has been update to reference the new course and the new
Eclipse version. In addition, the general pom.xml file has been updated
to include the newer versions of the dependencies, and the ear/pom.xml
has been modified to include more project information in the generated
EAR.

On the other hand, the testing mysql-ds.xml have been removed and the
standalone.xml testing files have been updated to include the datasource
data.

Missing version for compiler, javadoc, source and deploy plugin in POM was
causing some warning messages during the compilation with Maven.

In addition, the Javadoc was fixed in the OwnerService and PetService
classes.

SonarQube has a known problem with the 0.7.5 version of JaCoCo. This commit
solves this problem downgrading the JaCoCo version.

The source and javadoc of each proyect is deployed in the repository along with
the binaries.

The JaCoCo plugin has been added to perform the coverage test, while the
Wildfly plugins allows the automatic deployment of the project on a
Wildfly server using the 10990 port as the administration port.

This commit adds the JSF project with a web application that allows the
management of owners (by the administrators) and pets (by the owners).
The JSF project includes the functional tests for the owners management
page.

The EAR project only contains a POM that creates an EAR distribution of
the system.

The REST layer has been added but with incomplete tests. Students will
have to complete the tests.

This commit includes an important refactorization regarding tests. Test
classes and datasets have been moved from the "service" project to a new
"tests" project. This way, any project can include this "tests" project
as a dependency in order to have access to these common testing
resources.

This commit adds the OwnerService and PetService EJBs to the
implementation. This commit also includes the tests for this EJBs with
two different Wildfly profiles: a H2 profile and a MySQL profile.

Initial commit with a basic .gitignore, README.md and POM files.