Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

Bernardo-MG/dreadball-toolkit-webapp

Repository files navigation

Dreadball Toolkit Webapp

Web application for Dreadball.

Release docs Development docs

Release javadocs Development javadocs

Documentation

Documentation is always generated for the latest release, kept in the 'master' branch:

Documentation is also generated from the latest snapshot, taken from the 'develop' branch:

The documentation site sources come along the source code (as it is a Maven site), so it is always possible to generate them using the following Maven command:

mvn verify site -P h2,jetty

The verify phase is required, as otherwise some of the reports won't be created.

Usage

The application is coded in Java, using Maven to manage the project.

Prerequisites

The project has been tested on the following Java versions:

  • JDK 8

All other dependencies are handled through Maven, and noted in the included POM file.

Installing

The project can be installed by creating the war file and deploying it into a server.

Running

To run the project locally in an embedded server just use the following Maven command for Jetty:

mvn jetty:run-war -P h2,jetty,db-properties,development

Or this one for Tomcat:

mvn tomcat7:run-war -P h2,tomcat7,db-properties,development

After this the project will be accessible at [http://localhost:8080/].

Running tests

The integration tests require a database and a running server, and the easiest way to run them is in a similar way to running the project locally.

To run the tests with Jetty:

mvn verify -P h2,jetty,db-properties,development

To run them with Tomcat:

mvn verify -P h2,tomcat7,db-properties,development

Maven will run both the frontend and backend tests.

To run only the frontend tests:

npm run test

Packaging the WAR

When creating the WAR file the database connection credentials should be read from the environment:

mvn package -P production,mysql -D database.auth.source=env

Check the documentation for more information.

Collaborate

Any kind of help with the project will be well received, and there are two main ways to give such help:

  • Reporting errors and asking for extensions through the issues management
  • or forking the repository and extending the project

Issues management

Issues are managed at the GitHub project issues tracker, where any Github user may report bugs or ask for new features.

Getting the code

If you wish to fork or modify the code, visit the GitHub project page, where the latest versions are always kept. Check the 'master' branch for the latest release, and the 'develop' for the current, and stable, development version.

License

The project has been released under the MIT License.