On 10/27/06, Robert Harper <[EMAIL PROTECTED]> wrote:
Hello all, My project "A" depends on a 3rd party JAR "B" which has an accompanying DLL "C" (accessed through JNI). I have two questions that do not seem clearly addressed in existing documentation: 1) Must I structure these three files as different projects (each with its own POM) in my internal repository where "A" depends on "B" depends on "C"? Can DLL "C" not be packaged with its JNI wrapper "B" as one entry in the repo?
You can deploy the dll and the jar using one artifactId with 2 extensions via build-helper-maven-plugin's attach-artifact goal <artifacts> <artifact> <file>local location of your dll</file> <type>dll</type> </artifact> <artifact> <file>local location of your jni jar</file> <type>jar</type> </artifact> </artifacts> See build-helper-maven-plugin's doc for details -D 2) For the JNI stuff to work, my DLL "C" must be in my project "A"'s
executing directory and must have a specific filename "C.DLL" - not "C-2.1.1.DLL"! How can I ensure that my developers will be able to run project "A" on their local machine with "C.DLL" in their executing directory?
Use dependency-maven-plugin to copy the DLL to your specified location. This plugin also gives you option to rename and strip off the version of the dll Thanks in advance!
Rob Harper --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
