Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6
-
Fix Version/s: 1.7
-
Component/s: Maven Plugin
-
Labels:None
-
Number of attachments :
Description
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.
/**
* A list of signatures to include.
*
* @parameter
* @since 1.3
*/
private Signature[] includeSignatures = null;
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.