Github user thenatog commented on the issue:
https://github.com/apache/nifi/pull/3034
Let me know whether the way I've changed these dependencies is acceptable.
The dependencies that were modified were causing WARN messages to be shown when
NiFi started, for example:
```
2018-09-26 14:07:54,806 WARN [NiFi Web Server-21]
o.e.jetty.annotations.AnnotationParser javax.inject.Provider scanned from
multiple locations:
jar:file:///.../.../.../nifi/nifi-assembly/target/nifi-1.8.0-SNAPSHOT-bin/nifi-1.8.0-SNAPSHOT/work/jetty/nifi-update-attribute-ui-1.8.0-SNAPSHOT.war/webapp/WEB-INF/lib/javax.inject-1.jar!/javax/inject/Provi
der.class,
jar:file:///.../.../.../nifi/nifi-assembly/target/nifi-1.8.0-SNAPSHOT-bin/nifi-1.8.0-SNAPSHOT/work/jetty/nifi-update-attribute-ui-1.8.0-SNAPSHOT.war/webapp/WEB-INF/lib/javax.inject-2.5.0-b42.jar!/javax/inject/Provider.class
```
This was a result of the Jetty AnnotationParser scanning all classes for
annotations. It would add these to a list of scanned classes, and if a new
class is scanned which has a previous entry it emits a warning.
We saw these warnings for a few reasons:
* servlet-api was resolving as 'compile' rather than 'provided', causing it
to be included in two places and then scanned twice.
* Some libraries were transitive dependencies with older versions.
* Some transitive dependencies were what appeared to be repackaged
dependencies ie. bundled in a different package name but the same set of
classes within.
---
