Jörg,
thank you for this interesting idea. I think this would be the most
sophisticated ("most mavenic") solution, but I have the feeling that Dan's to
be simpler to set up in the short term for a Maven novice?
Thanks! :-)
Markus
> -----Original Message-----
> From: Jörg Schaible [mailto:[email protected]]
> Sent: Mittwoch, 27. Februar 2013 18:03
> To: [email protected]
> Subject: Re: How to tell Maven to put DLL dependency into
> java.library.path?
>
> Hi Marcus,
>
> Markus Karg wrote:
>
> > My POM declared a dependency to a DLL:
> >
> >
> >
> > <dependency>
> >
> > <groupId>net.sf.jacob-project</groupId>
> >
> > <artifactId>jacob-runtime</artifactId>
> >
> > <type>dll</type>
> >
> > <classifier>x64</classifier>
> >
> > <version>1.17-M2</version>
> >
> > <scope>runtime</scope>
> >
> > </dependency>
> >
> >
> >
> > (1) How can I tell Maven that when doing "mvn test", that DLL
> shall
> > be found on java.library.path, so that the JVM can load native
> classes
> > from it (using JNI)?
> >
> >
> >
> > (2) How can I tell Maven that it shall not statically be "x64",
> but
> > instead it depends on the architecture of the system actually
> > executing "mvn test" (e. g. "x86")?
>
> Have a look at the nar plugin. Create a JNI example project and have a
> look at the artifacts it will create. You may pack your DLLs into
> similar artifacts and then use this plugin to download and unpack the
> native stuff automatically when using those artifacts as dependency.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
