[
https://issues.apache.org/jira/browse/NIFI-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15674756#comment-15674756
]
Andy LoPresto commented on NIFI-3060:
-------------------------------------
I believe this was introduced in [PR
1237|https://github.com/apache/nifi/pull/1237] for [NIFI-3049]. I documented
some more information in [PR 1238|https://github.com/apache/nifi/pull/1238]:
{quote}
Also would like to get a fix for the logger stuff that was introduced in 1237
-- Maven build is fine but the tests that depend on asserting against
{{TestAppender}} fail in IntelliJ for multiple developers. Removing the
{{<exclusion>}} element for {{ch.qos.logback:logback-classic}} in
{{org.apache.nifi:nifi-properties-loader}} in
{{nifi-toolkit-encrypt-config/pom.xml}} resolves the test errors, but the built
toolkit has logging issues because of conflicting logging libraries in the
path.
{quote}
> ConfigEncryptionToolTest does not run successfully outside of maven test goal
> -----------------------------------------------------------------------------
>
> Key: NIFI-3060
> URL: https://issues.apache.org/jira/browse/NIFI-3060
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.1.0
> Reporter: Yolanda M. Davis
> Priority: Minor
>
> A recent change to exclude the logback-classic module prevents the ability to
> run the ConfigEncryptionToolTest class from running successfully outside of
> maven test goal (ie. running the test within IntelliJ). Approximately 7
> tests within the suite fail apparently due to their dependency on the
> TestAppender member class which is not appropriately populated with logged
> events as expected, causing any assertion against the TestAppender to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
