[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203975#action_203975
]
Brill Pappin commented on MOJO-574:
-----------------------------------
The problem is that when you are building another artifcat that depends it,
that other artifact needs the header files at least.
You want this to all be automatic and deployed as a natural process for
deploying a native artifact.
Not doing so renders the native artifact almost useless, and means that you
lose a lot of the power of setting it up as a maven build in the first place.
It definitely needs to be an option, but it should be on by default, and it
should be built into the plugin, so the usage and plan is consistent across
builds.
> .h files as dependencies
> ------------------------
>
> Key: MOJO-574
> URL: http://jira.codehaus.org/browse/MOJO-574
> Project: Mojo
> Issue Type: New Feature
> Components: native
> Environment: Windows and Unix (Linux)
> Reporter: Tony Sandin
>
> To compile or link native code requires static or shared libraries and
> include files. THe current Native plugin only deploy share, static, or
> executable artifacts, but no include files.
> Includes files should deploy with the library artifact as well.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
