[
https://issues.apache.org/jira/browse/MPLUGINTESTING-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPLUGINTESTING-46.
----------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> lookupConfiguredMojo should filter plugin configuration to mojo parameters
> --------------------------------------------------------------------------
>
> Key: MPLUGINTESTING-46
> URL: https://issues.apache.org/jira/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
> Priority: Major
>
> 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
(v7.6.3#76005)
