suggestion: continuous integration & automate maven publishing

[cesine]

I looked into #35. I was able to get it set up for you using continuous integration so that pushing to master can auto-publish new versions of the library (its also relatively easy to add it as a step in the build.gradle which you can run manually instead).

As part of this, I changed the requirement on pocketsphinx and sphinxbase to be set via an Environment Variable rather than needing to be installed in the same dir as this repo.

How this was tested

Resulting aar:

http://dl.bintray.com/cesine/educmupocketsphinx/pocketsphinx-android/5prealpha/

Verified build using the demo:

I added travis:

cmusphinx/pocketsphinx-android-demo#47

Then I used the artifacts
cesine/pocketsphinx-android-demo@f78626e

https://travis-ci.org/cesine/pocketsphinx-android-demo/builds/318603056

---

If you want to use continuous integration with travis, these are the steps you would have do. Getting this set up is complex, and when android build changes, the travis build does get out of date.

Bintray

• Create your user nshmyrev on https://bintray.com
• Create an organization edu.cmu.pocketsphinx on https://bintray.com
• In edu.cmu.pocketsphinx create a repository android

Travis

• Turn on travis for the pocketsphinx-android repo https://travis-ci.org/profile/cmusphinx
• Encrypt your travis key https://docs.travis-ci.com/user/deployment/bintray/#Encrypt-your-API-key and replace mine with yours
• push to this branch to trigger the build (i added you as a collaborator so you can push to my branch)

After the files are uploading to http://dl.bintray.com/edu.cmu.pocketsphinx/android/pocketsphinx-android/5prealpha/ then change the config to only upload new releases and to run only on the master branch:

• remove "override": 1
• remove all_branches: true

[nshmyrev]

Let me work on it, thank you!