I went ahead with a fix, and deployed a snapshot
On 9/11/06, dan tran [EMAIL PROTECTED] wrote:
Please file a JIRA so that ${project.build.directory}/classes will be add
to javah classpath.
However you can create your own jar project and make it a dependency of
the javah project.
Here is an
Hi Luis,
I think that your project organization is incorrect because you have a
circular dependence: your source code needs the JNI lib (example: for
runtime or testing purpose), and your library needs the java source code
to generate header files.
If you use a multi-modules project with
Hello all,
I am trying to build native classes with maven2 but there is an issue when
calling javah.
The things should happen in the following order:
i) Build the java source classes that have calls to JNI.
ii) Dump the class files into target/classes
iii) Using the
Please file a JIRA so that ${project.build.directory}/classes will be add
to javah classpath.
However you can create your own jar project and make it a dependency of the
javah project.
Here is an example.
http://svn.codehaus.org/mojo/trunk/mojo/maven-native/native-maven-plugin/src/it/jni/
-D
