LibraryDependencies management per project

Structure of dependencies similar to akka github project.
It's not similar in 100% because there is no need to have separate librariesDependencies per module.
It is because examples module depends on core module, so it has every of its libraryDependencies and I dont want to perform excluding.

Example:
exaples module has all dependencies of core module
core module cannot use StringUtils which can be used by examples module
Merge pull request #4 from ppiotrow/libraryDependencies

LibraryDependencies management per project
Documentation

From paper card created with Tomek in SubWay to README.md:)
Fixed documentation typos
Merge pull request #5 from ppiotrow/docFromSubway

Documentation
Aktor przechowujący genotyp

Aktor przechowuje genotyp i zwraca go jako odpowiedz.
Aktor przechowujący genotyp

Aktor przechowuje genotyp i zwraca go jako odpowiedz.
Tests asynchronous -> synchronous

Added trait to stop actor system after the test
Merge pull request #6 from ppiotrow/fenotype_actor

Aktor przechowujący genotyp
Evaluator actor

Actor receives ActorRef and its genome and returns actorRef with value of its genome

Changen convention: genome is now trait, not generic.
Its because of type erasure.
Generics were useless in pattern matching.
Merge pull request #7 from ppiotrow/evaluator

Evaluator actor