Upgrade shade plugin to version 2.1 to allow also to build the project with Maven 3.1
Exclude signature files from the shaded jar since it may throw a 'SecurityException: Invalid signature file digest for Manifest main attributes' when launching the application
Merge restx.factory.FactoryMachine provider-configuration file by adding a ServicesResourceTransformer in the shade plugin transfomers configuration
removed useless shade plugin's AppendingTransformer since jcsirot's ServicesResourceTransformer is far better
Provided xhanin's feedback pointer on the weird handling of route's urls
Appeared when handling of static resources was made by restx's classpath
This is not the best behaviour : a better behaviour would either :
 - To build a war file (thus have static resources in a dedicated webapps/ directory
 - Still better : to externalize static resources in a CDN and then package
 them in another project (something like a grunt-powered artefact)