language: java
jdk: oraclejdk8

script: mvn clean install -DskipTests

notifications:
  slack:
    rooms:
      - secure: H82Q57T5nRNDfVnxzlWZ2WoeGt71oq2eJGHbqJ4wP2tIc8b02UO9bztPKFxbm9slMu0JjxZdJfnHSgNZKfPVXrTqwPYRVjKqm7m9TynIlkQabV+yCI/oRvy4Xi/Xj7/aPvZat4s/bxjrtw9KwVdpmqWvRNNSgiTqQ4teBJ1uQGs=
    on_success: change
    on_failure: always

language: java
jdk: oraclejdk8

notifications:
  slack:
    rooms:
      - secure: H82Q57T5nRNDfVnxzlWZ2WoeGt71oq2eJGHbqJ4wP2tIc8b02UO9bztPKFxbm9slMu0JjxZdJfnHSgNZKfPVXrTqwPYRVjKqm7m9TynIlkQabV+yCI/oRvy4Xi/Xj7/aPvZat4s/bxjrtw9KwVdpmqWvRNNSgiTqQ4teBJ1uQGs=
    on_success: change
    on_failure: always

Enable running tests in Travis CI
Enable running tests in Travis CI

This change removes the custom `script` command, falling back to Travis
CI's default Maven script command, which, per [1] is:

    mvn test -B

The effect is that tests should now be run, which is particularly useful
for incoming pull requests.

See https://github.com/bisq-network/exchange/pull/1309#issuecomment-363776458
for context.

[1]: https://docs.travis-ci.com/user/languages/java/#Maven-Default-Script-Command
