[
https://jira.codehaus.org/browse/MPLUGINTESTING-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Fedorenko closed MPLUGINTESTING-42.
----------------------------------------
Resolution: Fixed
Implemented.
https://git-wip-us.apache.org/repos/asf?p=maven-plugin-testing.git;a=commit;h=46361087de813bc38004833d52cae7d766bf8e9d
> on-the-fly mojo execution configuration
> ---------------------------------------
>
> Key: MPLUGINTESTING-42
> URL: https://jira.codehaus.org/browse/MPLUGINTESTING-42
> Project: Maven Plugin Testing
> Issue Type: Improvement
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 3.2.0
>
>
> Currently, all mojo execution configuration parameters must be hardcoded in
> test pom.xml files. This makes it rather cumbersome to run multiple tests
> with the same test project but different mojo configuration. It'd be nice to
> be able to set mojo execution configuration parameters on the fly, as part of
> unit test code.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
