[
https://issues.apache.org/jira/browse/NIFI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661829#comment-14661829
]
Brandon DeVries commented on NIFI-404:
--------------------------------------
[~markap14], where in the NAR is the "native" directory supposed to go? I put
it at "foo.nar/META-INF/bundled-dependencies/native", then
"foo.nar/META-INF/native", then just "foo.nar/native"... nothing (except a
java.lang.UnsatisfiedLinkError"). If I take that same native directory and
drop in in the lib directory, and add
{code}
java.arg.11=-Djava.library.path=./lib/native
{code}
as before, that works. So... thoughts?
> 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)
