[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204032#action_204032
]
Brill Pappin commented on MOJO-574:
-----------------------------------
You don't actually need to use an special extensions for special bundles. If
the headers are kept separate, I think there is already a maven mechanism to
handle attached artifacts.
in fact if you want the source right now, you simply configure the source
plugin. See:
http://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html
http://docs.codehaus.org/display/MAVEN/Packaging+vs+Type+-+Derived+and+Attached+Artifacts
However I don't think automatically attaching all the source is a good idea,
because not all libraries are open (although the option to do so is a good
thing to have).
I think the key here is how the plugin sets up the build environment to
properly handle dependency header files as well as deploy them. All we really
need to do is be able to dynamically add to the <sources> configuration of the
native plugin (see:
http://mojo.codehaus.org/maven-native/native-maven-plugin/usage.html) so that
the headers are available during compile.
For deployment we do what the basic source plugin does and attache an artifact
that contains all the header files. We can simply filter the source dir for .h
file, or we put the headers specifically in src/main/headers or if relating to
MOJO-1321 then use src/main/native/include etc.
Question:
- Are the headers files usually platform dependent (baring headers for specific
platform includes like win32)?
FYI - One plugin that had to do something similar (download extra binaries and
make them available) was the get-maven plugin. See:
http://code.google.com/p/gwt-maven/
Anyway, nothing is going to happen until after the xmass holiday :)
> .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
