Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      0

      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?

        Activity

        Hide
        Robert Newson added a comment -

        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.

        Show
        Robert Newson added a comment - 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.
        Hide
        Michael Osipov added a comment -

        Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

        Show
        Michael Osipov added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

          People

          • Assignee:
            Unassigned
            Reporter:
            Robert Newson
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: