Currently there is no way to include a native library (DLL, dylib, so) in the packager contents and have it automatically accessible via the loadLibrary call. Including it with the other resources packages the DLL but does not add it to the library path. The user can sniff out URLs via the JarClassLoader and add that path, but it's an unsupported hack (that I wouldn't be suprised if it disappears in a security update).

I immediately see two possible approaches, (a) include the app dir in the library path, or (b) have a separate enumeration of files that are native libraries and include those in some other directory or in the same directory as the JVM dlls. There may be others.