Mojo Animal Sniffer

BuildSignaturesMojo exposes unused includeSignatures parameter

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6
  • Fix Version/s: 1.7
  • Component/s: Maven Plugin
  • Labels:
    None
  • Number of attachments :
    0

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;

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Stephen Connolly added a comment -

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.

Show
Stephen Connolly added a comment - 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.
Hide
Permalink
Zac Heismann added a comment -

Ah, thank you for explaining this to me.

Show
Zac Heismann added a comment - Ah, thank you for explaining this to me.

People

  • Assignee:
    Stephen Connolly
    Reporter:
    Zac Heismann
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: