language: java
jdk: oraclejdk8

notifications:
  irc:
    channels: chat.freenode.net#bitsquare
    template:
      - '%{message} (%{repository}#%{build_number}, %{duration})'
      - '%{repository}/%{branch} %{commit} %{author}: %{commit_message}'
      - '%{build_url}'
    on_success: change
    on_failure: always
    use_notice: true
    skip_join: true

env:
  - TERM=dumb

after_success:
  - ./gradlew jacocoTestReport coveralls

language: java
jdk: oraclejdk8

before_install: 
  - "export DISPLAY=:99.0"
  - "sh -e /etc/init.d/xvfb start"

notifications:
  irc:
    channels: chat.freenode.net#bitsquare
    template:
      - '%{message} (%{repository}#%{build_number}, %{duration})'
      - '%{repository}/%{branch} %{commit} %{author}: %{commit_message}'
      - '%{build_url}'
    on_success: change
    on_failure: always
    use_notice: true
    skip_join: true

env:
  - TERM=dumb

after_success:
  - ./gradlew jacocoTestReport coveralls

Use Xvfb to avoid 'cannot open display' warnings
Use Xvfb to avoid 'cannot open display' warnings

Builds began failing on Travis CI with the following message:

    Gtk-WARNING **: cannot open display:

This is because of tests like ViewLoaderTest, which now initialize the
JavaFX toolkit and expect a display in the process. This change starts
an Xvfb server (conveniently already available under Travis CI) in order
to provide a lightweight X11 environment and eliminate this problem.
