[
https://issues.apache.org/jira/browse/NIFI-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971597#comment-15971597
]
Joseph Witt commented on NIFI-3694:
-----------------------------------
Upgrading logback resulted in failures to start jetty due to classpath issues.
Logback-classic requires servlet-api when used in conjunction with Jetty and
since logback-classic was at the root classloader when our jetty classloader
went to load logback things it went to load servet-api things and failed. So
the solution is to move the servlet-api to the root lib. This is correct
anyway since our jetty-bundle is injected between all nars and the root anyway.
So we're not actually altering the exposure. Also needed to move the
jetty-schemas to the root lib as well for similar reasons.
After upgrading also needed to fix or remove tests written using reflective
calls to old logger implementations or which were looking at version specific
and non-functional output like InvokeHTTP tests were doing.
Finally had to update the logback.xml to use the latest recommended
configuration approaches and updated all NOTICE entries to logback 1.2.3.
> Update to latest logback to address configuration defects related to max log
> size/rollover
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-3694
> URL: https://issues.apache.org/jira/browse/NIFI-3694
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Tools and Build
> Affects Versions: 1.1.1
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Fix For: 1.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
