Hi Dan,
dan tran wrote:
Hi Richard,
The native-maven-plugin JNI example shows that you can have your native
project depends on a java jar project that has
java jni interfaces. This way you can use native plugin to generate jni
native include files before building the native artifacts.
This is the same behavior in maven1.
Not sure why it is a "blocking" to you since it works
The question is, how do you then arrange for another project (maybe with
more JNI, maybe not) to depend on that {native,java} project pair? It
all gets incredibly messy. And believe me, I tried.
Furthermore, what do you do about unit tests with the
native-maven-plugin? They have to run after the native artifacts are
built, obviously.
I don't mean to step on your toes by setting up an alternative to the
native-maven-plugin; it's just that the native-maven-plugin really
didn't suit my needs at all.
Cheers,
Richard
--
Richard van der Hoff <[EMAIL PROTECTED]>
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
