jasperproject/jasper-client — pull request #162 by Holzhaus (2014-09-10 17:19:59+00:00)
Title: Stop fiddling around with boot folder

**Important**: This PR is based on PR #161.

# Rationale

Right now, we have a lot files that do mostly the same and thus should be merged, because they are very confusing.

## Running Jasper
If you want to run Jasper, you can execute:
1. [boot/boot.sh](boot/boot.sh)
2. [client/start.sh](client/start.sh)
3. [boot/boot.py](boot/boot.py)
4. [client/main.py](client/main.py)

### Which one to execute?

The first two were taken care of in PR #161, but there are still two files the user can execute. Also, [client/main.py](client/main.py) is a bit hard to find without the documentation.
IMHO, the best solution is that there is *only one* python script in the main directory (i.e. `jasper.py`) that runs jasper.

## Running (unit)tests
If you want to run unittests, you can execute:
1. [boot/test.py](boot/test.py)
2. [client/test.py](client/test.py)

### What's the difference?

The first script simply a Unittest for `vocabcompiler`. The second one is for everything else.
Chances are, that in most cases you want to run them both.

# What has been changed?

1. All jasper startup scripts/modules have been merged into `jasper.py`.
2. All former startup script has been made simple wrappers that call jasper.py to maintain backwards-compatability for existing installations.
3. `vocabcompiler.py` has been moved to the client folder (which is a package now)
4. The `boot/test.py` script (vocabcompiler) has been merged into `client/test.py` and the travis file has been updated

## Running Jasper
You don't need to change your existing installations. New installations can just call `jasper.py` directly.

## Running (unit)tests
You only need to run `client/test.py`. If you want to test vocabcompiler, too, then simply add `--vocabcompiler` as command line argument.