Set up continuous integration

[gberche-orange]

compile, run unit tests, package as a jar/war, run acceptance tests, create a maven release, upload the release into the github repo

[gberche-orange]

@s-bortolussi Thanks for the travis-ci integration.

Would be great to enhance the travis-ci release script in the following ways:

• avoid having variations in the name of the produced war (currently static-creds-broker-1.1.war) across release, as to:
  • avoid the need to manually update the deployment procedure
  • be able to hardcode the relative path to the binary in manifest.yml with "path" property
• find a better name for the enclosing directory (currently "to-release") suggesting "static-creds-broker" instead, and investigate if there is a way to directly include the war file into "."