[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567377#comment-14567377
]
Matt Gilman commented on NIFI-632:
----------------------------------
I noticed the cyclical dependency when I attempted to fix the issue locally
just to confirm that is what it was. I didn't think that NIFI-633 would have
had the same problem. I sort of assumed that the logger would have also been
mocked out. We don't really have that luxury here. That's why I added the
comment saying that we need to do some refactoring and shuffling to get it
right.
In a multiple module project, the parent pom should be the artifact in it's
parent directory.
> Documentation Generation: Nar ClassLoader
> -----------------------------------------
>
> Key: NIFI-632
> URL: https://issues.apache.org/jira/browse/NIFI-632
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.1.0
> Reporter: Matt Gilman
> Assignee: Dan Bress
> Priority: Minor
> Fix For: 0.1.1
>
> Attachments: 0001-my-squashed-commits-for-NIFI-632.patch
>
>
> When auto generating component documentation the NarThreadContextClassLoader
> needs to be set in case the component attempts to load anything off of its
> classpath. Without this, the documentation generation fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
