You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tobias Oberlies (JIRA)" <ji...@codehaus.org> on 2015/01/05 12:08:14 UTC

[jira] (MPLUGINTESTING-46) lookupConfiguredMojo should filter plugin configuration to mojo parameters

Tobias Oberlies created MPLUGINTESTING-46:
---------------------------------------------

             Summary: lookupConfiguredMojo should filter plugin configuration to mojo parameters
                 Key: MPLUGINTESTING-46
                 URL: https://jira.codehaus.org/browse/MPLUGINTESTING-46
             Project: Maven Plugin Testing
          Issue Type: Improvement
         Environment: maven-plugin-testing-harness 3.0.0, but later versions are also affected AFAIK
            Reporter: Tobias Oberlies


lookupConfiguredMojo attempts to set the entire plugin configuration on the mojo. This fails if the plugin configuration includes parameters that don't exist in the mojo.

Arguably, this is a feature because it helps detecting incorrect/irrelevant test configuration. However, this prevents that two mojos from the same plugin can be executed. The use case for such an approach would be to run one mojo as test setup for a second mojo.

So I'd like to propose that lookupConfiguredMojo filters the plugin configuration to the mojo parameters (like in finalizeMojoConfiguration). This should either be done always, or only if enabled via a new method parameter.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)