maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Curtis Rueden <>
Subject Re: DLL Artifact
Date Wed, 05 Jun 2013 14:59:55 GMT
Hi Andy,

> I have the classic jar and dll

If you want an even simpler solution, you can build the DLL outside Maven
(with e.g. CMake), then put the DLL into src/main/resources so that it is
included in the JAR, then use native-lib-loader [1] at runtime to load the


P.S. Of course, if your DLL is large it will bloat your SCM repository
unless you use something like git-annex [2].


On Wed, Jun 5, 2013 at 7:26 AM, Andy <> wrote:

> Hi All,
> I have searched to death the jni project solutions and would just like a
> simple solution to a trivial issue, but having difficulty pulling it off.
> I have the classic jar and dll (I am really not interested the native
> plugin or packaging the dll in a jar yet, etc. I just don't have the time
> right now).
> I know I can manually deploy the dll artifact to our repo and declare a
> dep etc, then use the dependency module to get it - This is what I've done
> so far as a quick fix.
> What I'd like to do is more simple than that in the long run. I want to
> have the jar and dll projects as modules in a multi-module pom, that's done.
> parent----jar/pom.xml
>          |----dll/pom.xml
>          |----dll/
> Now I'd just like the dll/pom.xml to say 'do not package a jar, then
> deploy the dll as the artifact.
> To disable the jar is easy enough...
> <execution>
>     <id>default-jar</id>
>     <phase>none</phase>
> </execution>
> ...but how to get the dll to automatically deploy on the deploy phase?
> I know I've see it done somewhere, but just can't find what I need. Thanks
> in advance.
> Andy.
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**<>
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message