There are some hard problems in handling JNI. First, while you can set java.library.path, you can't set PATH or LD_LIBRARY_PATH or DYLD_LIBRARY_PATH, which you need on Windows, Linux/Solaris, or MacOS respectively.
If you really plan to retrieve the shared objects as maven artifacts, then they will arrive in your local repo, and you have to set these environment variables to the directories where they land. If you want to support multiple platforms, you have to worry about that. Classifiers might be helpful for this. It has seemed to me that perhaps a creative mashup of OSGi and maven might produce something handy here, since OSGi bundles/fragments can carry native libs, and the OSGi runtime undertakes to get all the environment variables and such set up for you. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
