Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2933
2018-08-02 16:20:07,347 WARN [NiFi Web Server-21]
o.e.jetty.annotations.AnnotationParser javax.inject.Inject scanned from
multiple locations:
jar:file:///Users/jwitt/Development/joewitt-nifi.git/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/Inject.class,
jar:file:///Users/jwitt/Development/joewitt-nifi.git/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/Inject.class
2018-08-02 16:20:07,348 WARN [NiFi Web Server-21]
o.e.jetty.annotations.AnnotationParser javax.inject.Named scanned from multiple
locations:
jar:file:///Users/jwitt/Development/joewitt-nifi.git/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/Named.class,
jar:file:///Users/jwitt/Development/joewitt-nifi.git/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/Named.class
2018-08-02 16:20:07,348 WARN [NiFi Web Server-21]
o.e.jetty.annotations.AnnotationParser javax.inject.Provider scanned from
multiple locations:
jar:file:///Users/jwitt/Development/joewitt-nifi.git/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/Provider.class,
jar:file:///Users/jwitt/Development/joewitt-nifi.git/nifi-assembly/target/nifi-1.8.0-SNAPSHOT-bin/nifi-1.8.0-S
2018-08-02 16:20:16,335 WARN [main]
o.e.j.webapp.StandardDescriptorProcessor Duplicate mapping from / to default
2018-08-02 16:20:16,429 WARN [main] o.e.jetty.annotations.AnnotationParser
Unknown asm implementation version, assuming version 393216
Todo:
- identify source of and cleanup warnings that now show up on application
startup
- test/what if one just copied the contents of a new lib dir on top of
their old lib dir as an upgrade process...will our work dirs get cleaned and
restart properly
- add docs in the unpack method to explain why we move
META-INF/bundled-dependencies to NAR-INF/bundled-dependencies
- this is just a technique to work with older/current nar creation
approach.
- this is done because jetty's code assumes that META-INF is only in a
directory path once or else it fails to find some tlds.
- but we want to keep META-INF for things like META-INF/MANIFEST.mf and
maven bits.
- we might want to just move META-INF/bundled-dependencies to
bundled-dependencies. The 'NAR-INF' part is not value add since the nar
metadata is in META-INF/MANIFEST.mf and not easily moved due to jar/manifest
loading code
- file a JIRA to change where we write them in the nar plugin to
NAR-INF/bundled-dependencies directly
- Test secure/non-secure clusters/etc..
---
