I'd suggest you do add each of the binaries of the library as separate artifacts. Then you could use the normal dependency machanism of Maven. Write a simple shell script that deploys all of the binaries to your repo whenever they are update. That shell script could do pretty much anything you want to; for example, unpack a distro zip and then deploy each of the artifacts.
As written here many times, don't fight the Maven way! /Anders On Sat, Dec 26, 2009 at 15:23, Tich <[email protected]> wrote: > Hello, > > I need to use a JNI library in multiple modules of my maven project. The > binaries of this library (dll and jars) are frequently updated so I don't > want to manually add each file of the distribution to the maven repository. > So I decided to write a maven module that packages all the files of the JNI > library in a zip file and now I would like to automatically add the jars of > this archive to the dependencies of any other maven modules that need them > at compile time. > As I am new to maven, I don't see what is the best way to do this. > > Could someone help me ? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
