move back to having relativePath in the pom for the parent.

this is necessary in order to get a build on a machine that has never
built before to work.
move exhaustive tests to their own package.

Alas, with the decision to separate the integration tests into a
different jar, and signing jars, we run into a java exception if I use
io.humble.ferry as the package name for these tests.

The unfortunately side effect of this is I have to make a
package-private member of JNIMemoryManager public.
add developerConnection
attempt #2 and getting developer connections right
partial steps on release process
get it parent back in pom
changes in build instructions
add generated version files -- they will not change per run
stop generating pom.xmls
more instructions
peg to 0.1.1
markdown changes
fix version and add some sources so we can make a -sources artifact.
skip tests if skipTests property is defined
Merge branch 'release/v0.1.1'
Merge branch 'master' of github.com:artclarke/humble-video