The following comment has been added to this issue:
Author: Robert Newson
Created: Thu, 2 Sep 2004 6:39 PM
Body:
FYI: This appears to only be a requirement for WIN32.
I can run the native:jniheader goal successfully with the default properties.
The class I'm generating the header file extends an abstract class from one of my
declared dependencies.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPNATIVE-9?page=comments#action_23744
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPNATIVE-9
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPNATIVE-9
Summary: Allow control over classpath
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-native-plugin
Assignee:
Reporter: Robert Newson
Created: Thu, 2 Sep 2004 5:43 PM
Updated: Thu, 2 Sep 2004 6:39 PM
Description:
At present the plugin only adds ${maven.build.dest} to the classpath.
I need to be able to include some of my dependencies on the classpath when compiling
JNI headers (I'm implementing an interface from another library with JNI).
For my purposes, including my jar dependencies on the classpath will be fine, but
maybe a dependency property (<jni>?) would be neater in the long term?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
