在Web应用程序中使用本机Maven工件(nar)

我有一个使用maven-nar插件构建和打包的本地共享库.这很好用，并且可以在Linux/MacOSX/Windows上构建.我还定义了一个JNI库，该库也使用maven-nar构建，用于包装共享库.这两个都是作为NAR工件生成的，并且需要使用maven-nar插件才能使用.

I have a native shared library that is built and packaged using the maven-nar plugin. This works great and builds on Linux/MacOSX/Windows. I've also defined a JNI library, also built using maven-nar, that wraps the shared library. Both of these are produced as NAR artifacts and require the maven-nar plugin in order to be used.

当从非NAR打包项目中声明对这些NAR的依赖关系时，就会出现问题. maven-nar插件似乎从未被调用.只有当我将项目的包装更改为NAR时，maven-nar插件才会启动.这使得NAR包装似乎需要具有传染性才能起作用，如果存在NAR依赖性，则所有上游项目都需要进行NAR包装.这是正确的还是我错过了什么?

The problem arises when declaring a dependency on these NARs from a non-NAR-packaged project. The maven-nar plugin never seems to get invoked. Only when I change the project's packaging to NAR does the maven-nar plugin kick in. This makes it seem like NAR packaging needs to be infectious in order to work, if there's a NAR dependency then all upstream projects need to be NAR-packaged. Is this correct or am I missing something?

使用maven-nar插件生成的本机共享库和JNI工件能否成功用于Web应用程序(即WAR)中?如果可以在WAR中使用和部署它们，该怎么做?否则，是否是将本机库手动放置在应用程序服务器上java.library.path中某个位置的唯一选择?

Can the native shared library and JNI artifacts produced using the maven-nar plugin be successfully used in web applications, i.e. WARs? If they can be used and deployed in a WAR, how is it done? Otherwise, is the only option to manually place the native libraries in some location in the java.library.path on the app server?

以下是该项目的POM的代码段，该代码段取决于NAR JNI工件:

Here's a snippet of the POM for the project that depends on the NAR JNI artifact:

  <?xml version="1.0" encoding="UTF-8"?>
  <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>thegroup</groupId>
    <artifactId>theparent</artifactId>
    <version>1.0-SNAPSHOT</version>
    <relativePath>../pom.xml</relativePath>
  </parent>

  <artifactId>thedependant</artifactId>
  <packaging>jar</packaging>
  <name>A nice name</name>

  ...

  <properties>
    <skipTests>true</skipTests>
  </properties>

  ...

  <build>
    <plugins>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-nar-plugin</artifactId>
         <version>2.1-SNAPSHOT</version>
       </plugin>
    </plugins>
  </build>

  ...

  <dependencies>
    <dependency>
      <groupId>thegoup</groupId>
      <artifactId>theJNI</artifactId>
      <version>1.0-SNAPSHOT</version>
      <type>nar</type>
    </dependency>
  </dependencies>

  ...

</project>