Initial commit: Added redis download skeleton with internal servers, added make skeleton provisioned by the OS

* working runtime configuration for in-house redis binaries
* use added daemon process setting to disable shutdown hook for redis-cli

- fixed all test cases
- added support for directory parameter
- some refactoring, tried to clean out all mongo references
- removed dead code
- added internally deployed artifact version numbers

- change parent pom to DW-internal pom to be able to deploy snapshots

- reference correct @include for markdown test

- added src/ets license foles

- added process Id and data storage directory and file parameters
- refactoring to avoid class name collisions

Setup proper port for redis in testcases

- ignore bitSize for downloading the binaries because JVM lies about native bitsize

- adjusted test case

flapdoodle Redis service start cannot start up process on Windows
* add support for getting the running status of a process
* fixed some old mongo references

flapdoodle Redis service start cannot start up process on Windows
* added testcase for isProcessRunning()

flapdoodle Redis service start cannot start up process on Windows
* prevent stackoverflow for the stop redis cli command

flapdoodle Redis service start cannot start up process on Windows
* proper support for nested calling redis cli

flapdoodle Redis service start cannot start up process on Windows
* added nesting debug
* increased shutdown waiting timeout

flapdoodle Redis service start cannot start up process on Windows
* do not reuse runtime configs for testcase, otherwise it assumes nesting

flapdoodle Redis service start cannot start up process on Windows
* disable cli usage for killing for now

flapdoodle Redis service start cannot start up process on Windows
* re-enabled cli because test cases won't run without it. would need a solution for memcached for the same problem.

flapdoodle Redis service start cannot start up process on Windows
* added proper pid file creating waiting handling

flapdoodle Redis service start cannot start up process on Windows
* increase source compatibility level to 1.7

flapdoodle Redis service start cannot start up process on Windows
* removed Java 1.7 dependency
* moved up common functions for pid file handling to flapdoodle-process

stopRedisInstance() using the redis-cli gets into a loop
* added debu logging
* set isNested() manually

stopRedisInstance() using the redis-cli gets into a loop
* updated to latest redis artifact version to consume 32 bit windows redis binary

stopRedisInstance() using the redis-cli gets into a loop
* adjusted test case

stopRedisInstance() using the redis-cli gets into a loop
* removed debug logging
* use proper getter/setter for nested field

* always delete pid file

* preparing release: updated pom with new versions, developer connection, disabled signing

switched to new flapdoodle.process pom

* adjusted to new flapdoodle.process version

[maven-release-plugin] prepare release de.flapdoodle.embed.redis-1.0_1

[maven-release-plugin] prepare for next development iteration

* adjustments to new process framework

* switched to latest flapdoodle process internal release 1.33_1

* formatted everything flapdoodle style
* externalized server URL to properties file, see server.properties.sample

* updated pom to reflect sonatype parent pom
* adjusted to new API
* updated readme