[MRESOLVER-36] Change internal logging to sl4j

This closes #8
This restores the OSGi metadata that was lost in the switch from
Eclipse Aether to Maven Resolver and allows maven-resolver to be
used in OSGi runtime environments.

This closes #12

Compiling a pattern is a rather expensive operation and doing it
a user-convenient constructor is very hurtful. Cache the compiled
pattern in a static final field, just like other classes in this
artifact do.

This closes #16

Revert sleep back to 100 ms

org.apache.httpcomponents:httpclient .................. 4.5.3 -> 4.5.4
org.apache.httpcomponents:httpcore .................... 4.4.6 -> 4.4.8
org.codehaus.plexus:plexus-utils ..................... 3.0.24 -> 3.1.0
org.eclipse.sisu:org.eclipse.sisu.plexus .............. 0.1.1 -> 0.3.3
org.sonatype.sisu:sisu-guice .......................... 3.1.6 -> 3.2.6

org.eclipse.jetty:jetty-server .... 9.2.9.v20150224 -> 9.2.23.v20171218
org.eclipse.jetty:jetty-servlet ... 9.2.9.v20150224 -> 9.2.23.v20171218
org.eclipse.jetty:jetty-util ...... 9.2.9.v20150224 -> 9.2.23.v20171218

Plugins:
maven-invoker-plugin:3.0.1
junit:junit:4.12
org.eclipse.sisu.plexus:0.3.3

This closes #11

[WARNING] Error injecting: org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor
java.lang.NoClassDefFoundError: org/apache/maven/plugins/annotations/Execute
    at java.lang.ClassLoader.defineClass1 (Native Method)
    at java.lang.ClassLoader.defineClass (ClassLoader.java:763)

Resolution without MRESOLVER-9 looks like (Maven 3.3.9):

[DEBUG]    org.sonatype.sisu:sisu-guice:jar:no_aop:3.2.6:compile
[DEBUG]       javax.inject:javax.inject:jar:1:provided (scope managed from compile by org.apache.maven.resolver:maven-resolver:1.1.1-SNAPSHOT)
[DEBUG]       com.google.guava:guava:jar:16.0.1:compile

The 'javax.inject:javax.inject:jar:1:provided' line shows that the artifact
is in 'provided' scope. The Maven resolver without MRESOLVER-9 fixed will
incorrectly resolve that transitive provided dependency. With MRESOLVER-9 fixed,
the resolver correctly no longer resolves transitive provided dependencies. That
dependency needs to be declared directly.

[MNG-6141] Dependency management overrides are not transitive and should be considered an anti-pattern.

o Added transport modules to the parent dependency management and removed all
  dependency management overrides from the demo modules.

Signed-off-by: Manfred Moser <manfred@simpligility.com>
Signed-off-by: Manfred Moser <mmoser@apache.org>

Signed-off-by: Manfred Moser <manfred@simpligility.com>
Signed-off-by: Manfred Moser <mmoser@apache.org>

Signed-off-by: Manfred Moser <manfred@simpligility.com>
Signed-off-by: Manfred Moser <mmoser@apache.org>

- added module
- updated parents
- synced versions

Signed-off-by: Manfred Moser <manfred@simpligility.com>
Signed-off-by: Manfred Moser <mmoser@apache.org>

Signed-off-by: Manfred Moser <manfred@simpligility.com>
Signed-off-by: Manfred Moser <mmoser@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>

Signed-off-by: olivier lamy <olamy@apache.org>