Before I can jump to some sort of answer, first:

1. How do you build your jni and native libraries currently?

2. Is your native build multiplatform or windows only?

3. Do you have a need to download external native libraries and
corresponding include files for your build?

-D


On Sun, Jun 14, 2009 at 4:28 AM, <[email protected]> wrote:
> Hello, I have a multiproject application that I want to port to maven.
> I've managed to mavenize several of the projects that are pure Java with
> apparently no error. So, my first impression is great. Now, I'm facing a
> new challenge. One of the projects is using JNI and I have no idea about
> if maven can handle this. I have seen several plugins supposed to do this
> job, but I'm not sure after reading the one-page documentation about how
> to proceed.
>
> In a first phase, it is enough for me if I can make Maven to download the
> compiled dll's, just because they are dll and no so. The libraries are
> windows meant, so that is why I can go on using them as regular files.
>
> In this matter, my question is how to make maven to download them. Is it
> in the "package" goal?
>
> Once this is fixed, in order to run tests I need to pass the
> -Djava.library.path=/path/to/dll argument to the JVM. Is there any way to
> have maven to compose this automatically? since they can be several, and
> according to the maven repository layout they can be stored in different
> folders. It would be nice if all the folder paths can be automatically
> passed to the java.library.path argument.
>
>
> If I achieve this then I'll feel very happy. But if can also port the
> build of the native libraries to maven it would be perfect. Does anyone
> have some tips for me? I would specially appreciate examples because I
> have already read the yet-another-only-one-page documentation of the
> native and the freehep plugins.
>
> Please, keep in mind that my experience in Maven is only for 4 days.
> Thank you all in advance.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to