Home/ Questions/Q 8313703
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T20:34:46+00:00

My multimodule project contains 10 modules 3 of which require a 3rdparty jni. The

  • 0

My multimodule project contains 10 modules 3 of which require a 3rdparty jni. The three must unpack the jni artifact and add its location to LD_LIBRARY_PATH for test execution.

What’s the elegant maven way to handle this situation?

  • Add dependency, unpack via maven-dependency-plugin execution surefire property to the three modules (violates dont-repeat-yourself principle and won’t scale).
  • Use a profile in central pom for these steps and activate it with needsFooJni property (profiles aren’t per module and should be used for platform or other build-wide needs)
  • Use executions controlled by properties in top level pom (seems a little fragile).

So, What’s the elegant maven way to handle this kind of situation so my native dependencies are used in the test phase.

Thanks

Peter

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I opted for this solution:

    • Add top level properties for the default JNI location. In the example below, I’ve also added a “special” case for a JNI that required a specific structure to locate additional resources.
      `${project.basedir}/target/extracted
      ${project.basedir}/target/cache/special
      ${extractedJniCache}${path.separator}${specialExceptionLibrayCache}’

    • Add properties to control extraction

      <skipSpecialJNIExtraction>true<skipSpecialJNIExtraction>
      <skipFooBarJNIExtraction>true<skipFooBarJNIExtraction>

    • Define dependency extraction executions controlled by skip properties (default is to skip and individual modules can override

    • In my surefire configuration define path and ld library path
      <environmentVariables>
      <PATH>${env.PATH}${path.separator}${ldLibraryAddon}</PATH>
      <LD_LIBRARY_PATH>${ldLibraryAddon}</LD_LIBRARY_PATH>

      `

    By default, all tests add directories for the JNIs to PATH/LD_LIBRARY_PATh for test execution. These directories will only exist if the module overrides the skip properties.

    It’s not as elegant as I’d like, but it is centralized to the master pom keeping complexity in one place and keeping the module poms small.

    • 0