[
http://jira.codehaus.org/browse/MANIMALSNIFFER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MANIMALSNIFFER-16.
------------------------------------------
Resolution: Fixed
Fix Version/s: 1.7
r14058.
The parameter was left over rubbish. The correct way to include signatures is
to list them as dependencies in the module creating the signature as this
allows Maven to construct a correct build plan when you have a multi-module
build with multiple signatures being created.
> BuildSignaturesMojo exposes unused includeSignatures parameter
> --------------------------------------------------------------
>
> Key: MANIMALSNIFFER-16
> URL: http://jira.codehaus.org/browse/MANIMALSNIFFER-16
> Project: Mojo Animal Sniffer
> Issue Type: Bug
> Components: Maven Plugin
> Affects Versions: 1.6
> Reporter: Zac Heismann
> Assignee: Stephen Connolly
> Fix For: 1.7
>
>
> The BuildSignaturesMojo exposes the includeSignatures parameter, but it does
> nothing with it. I assumed it would merge an existing signature file with
> one it would generate for my project. I was intending to use this feature to
> include the org.codehaus.mojo.signature:java16:1.0 signature file.
> {code}
> /**
> * A list of signatures to include.
> *
> * @parameter
> * @since 1.3
> */
> private Signature[] includeSignatures = null;
> {code}
--
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
