[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580604#comment-14580604
]
Dan Bress commented on NIFI-632:
--------------------------------
Mark,
Will do VolatileContentRepository and VolatileFlowFileRepository.
I may be missing a provenance repo too. Will double check that.
Also, I noticed you opened
[NIFI-674|https://issues.apache.org/jira/browse/NIFI-674] which I addressed in
here. How do you want to handle that?
Honestly, I could see a case being made for four tickets total for all the
things I mentioned(you already created in in NIFI-674), and pulling the fixes
out of this branch and putting it in the respective tickets. Then leave this
ticket JUST for fixing Matt's original finding. What do you think? Overkill?
> 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.2.0
>
> Attachments: 0001-Squashed-commit-of-the-following.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)
