You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Fedorenko (JIRA)" <ji...@codehaus.org> on 2012/05/20 17:01:03 UTC
[jira] (MPLUGINTESTING-23) Provide a way to create fully configured
mojo instance
Igor Fedorenko created MPLUGINTESTING-23:
--------------------------------------------
Summary: Provide a way to create fully configured mojo instance
Key: MPLUGINTESTING-23
URL: https://jira.codehaus.org/browse/MPLUGINTESTING-23
Project: Maven 2.x Plugin Testing
Issue Type: New Feature
Components: plugin-testing-harness
Affects Versions: 2.0-alpha-1
Reporter: Igor Fedorenko
As of version 2.0-alpha-1, plugin-testing only provides a way to lookup and instantiate uninitialized mojo instances, which means significant amount of explicit configuration in test pom.xml files and in test java code is required in order to be able to execute the mojo. It would be nice to be able to request fully configured mojo instances, that are initialized according to mojo parameter expressions and default values, thus saving the overhead of maintaining the manual mojo configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGINTESTING-23) Provide a way to create fully configured
mojo instance
Posted by "Igor Fedorenko (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MPLUGINTESTING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Fedorenko closed MPLUGINTESTING-23.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Introduced new AbstractMojoTestCase.lookupConfiguredMojo. which returns fully configured Mojo instance. Unlike other lookupMojo methods, lookupConfiguredMojo uses maven plugin parameter default values, so test can use much smaller and
easier to maintain pom.xml files.
Also introduced AbstractMojoTestCase newMavenSession and newMojoExecution helper methods. These helpers are used by lookupConfiguredMojo but should be useful in other cases.
http://svn.apache.org/viewvc?view=revision&revision=1185951
> Provide a way to create fully configured mojo instance
> ------------------------------------------------------
>
> Key: MPLUGINTESTING-23
> URL: https://jira.codehaus.org/browse/MPLUGINTESTING-23
> Project: Maven 2.x Plugin Testing
> Issue Type: New Feature
> Components: plugin-testing-harness
> Affects Versions: 2.0-alpha-1
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 2.0
>
>
> As of version 2.0-alpha-1, plugin-testing only provides a way to lookup and instantiate uninitialized mojo instances, which means significant amount of explicit configuration in test pom.xml files and in test java code is required in order to be able to execute the mojo. It would be nice to be able to request fully configured mojo instances, that are initialized according to mojo parameter expressions and default values, thus saving the overhead of maintaining the manual mojo configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira