Cleanup, simplify and overall improve sw360chores

[maxhbr]

The new entry point for controlling is /sw360chores.pl.

Features / changes

previously: /deployment/docker-compose.sh

This is replaced by /sw360chores.pl. Its usage is documented within the script.

the folder /deployment

Instead of Dockerfiles and docker-compose configuration this folder now only contains the docker-compose files. The docker images are are build from instructions in the folder /docker-images

previously: sw360_dependencies.tar.gz and the folder /packaging

The new configured tomcat is created via the folder /miscellaneous/prepare-liferay and is called sw360-liferay.tar.gz. It does no longer contain couchdb-lucene by default. The couchdb-lucene war can be created by the script in /miscellaneous/couchdb-lucene.

The generated sw360-liferay.tar.gz is preconfigured with a portal-bundle.properties which is configured to load /etc/sw360/portal-ext.properties.

in dev mode are logs served under ...:8443/logs

This is copied from https://github.com/sw360/sw360chores/pull/28.

Testing

A simple way of testing via Virtualbox is to:

• copy all war files to _deploy
• call vagrant up && vagrant reload
• call vagrant ssh -c "/sw360chores/sw360chores.pl -- logs -f"

travis

This PR contains the travis configuration from https://github.com/sw360/sw360chores/pull/31 which might help testing.

[maxhbr]

The travis tests are again randomly failing...

[maxhbr]

I will rebase and squash once the code is tested