[
https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567363#comment-14567363
]
Dan Bress commented on NIFI-632:
--------------------------------
Matt, yes they should be independent. I made both changes in their own
branches off of develop, so I think they should be independent. Though I'm
worried this one may face the same cyclic dependency issue you brought up
earlier.
I used the archetype to create the example bundle, and I had to tweak a few
things, so maybe I got the parent pom wrong.
It is set to:
{code:xml}
<parent>
<groupId>org.apache.nifi</groupId>
<artifactId>nifi-nar-bundles</artifactId>
<version>0.1.1-incubating-SNAPSHOT</version>
</parent>
{code}
What should it be?
> 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)
