[
https://issues.apache.org/jira/browse/NIFI-12640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808728#comment-17808728
]
ASF subversion and git services commented on NIFI-12640:
--------------------------------------------------------
Commit e66da895fcf916b46d1f85bde454f1faf511a65e in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e66da895fc ]
NIFI-12640 Moved servlet-api and jetty-schemas to nifi-jetty-bundle (#8272)
- Set Jetty AnnotationConfiguration log level to WARN suppressing informational
messages related to Logback ServletContainerInitializer
> Move servlet-api and jetty-schemas to jetty-bundle
> --------------------------------------------------
>
> Key: NIFI-12640
> URL: https://issues.apache.org/jira/browse/NIFI-12640
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 2.0.0-M2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Following framework upgrades to Jetty 12, the servlet-api and jetty-schemas
> JAR libraries can be relocated to the nifi-jetty-bundle NAR instead of the
> application lib directory.
> NiFi 1.2.0 moved servlet-api and jetty-schemas to the root lib directory due
> to Jetty loading issues with the AnnotationConfiguration class. Jetty 12 logs
> an informational message when attempting to load the Logback
> ServletContainerInitializer, but does not have any runtime issues. NiFi uses
> a configured shutdown hook instead of the ServletContainerInitializer, so
> loading the Logback implementation is not required, allowing the servlet-api
> JAR to be relocated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
