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 -Dan On 6/14/06, Richard van der Hoff <[EMAIL PROTECTED]> wrote:
A while ago, I posted here asking for help with using Maven to handle projects which make use of JNI code. I was met by a stony wall of silence at that time... Anyway, a month later, and after quite a lot of thinking, hacking and tweaking, I've come up with a solution I'm reasonably happy with. I've written it all up at http://docs.codehaus.org/display/MAVENUSER/Projects+With+JNI, in the hope that it may be useful to others. Feedback is welcome, although bear in mind that I've spent long enough on this now that I may be reluctant to do much more work :). Cheers, Rich -- 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]
