You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Brandon DeVries (JIRA)" <ji...@apache.org> on 2015/07/31 15:06:04 UTC
[jira] [Commented] (NIFI-404) Update developer guide to explain the
NAR's Native Library isolation in addition to ClassLoader isolation
[ https://issues.apache.org/jira/browse/NIFI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649194#comment-14649194 ]
Brandon DeVries commented on NIFI-404:
--------------------------------------
[~markap14], i could use this info... right now i've added a line to the bootstrap.conf like
{code}
java.arg.11=-Djava.library.path=./lib/native
{code}
if those libraries were part of / loaded with the NAR that needed them that would probably be better. If you've got that handy so I don't have to figure it out again, I'd aprpeciate it...
> Update developer guide to explain the NAR's Native Library isolation in addition to ClassLoader isolation
> ---------------------------------------------------------------------------------------------------------
>
> Key: NIFI-404
> URL: https://issues.apache.org/jira/browse/NIFI-404
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Reporter: Mark Payne
>
> Need to explain that native libraries existing in the native/ directory are isolated to that NAR and explain how to add native libraries to that directory via Maven.
> Our documentation for how the NAR Classloader works and its purpose does not clearly call out the limitations. For example, if one wants to use some version of Jetty or logback can they? How so? We need to show a clear diagram of how the NAR classloading works and so on so folks can more readily reason over it.
> NAR stuff is very powerful and helpful but today it is a bit too magical without this complete documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)