[jira] Closed: (MNG-17) Improve the validation of mojo parameters

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-17?page=all ]
     
Brett Porter closed MNG-17:
---------------------------

    Fix Version:     (was: 2.0-alpha-2)
     Resolution: Won't Fix

not applicable to new mojo api. Will need an alternative solution (eg validator classes) when we get back to providing tools support for mojos.

> Improve the validation of mojo parameters
> -----------------------------------------
>
>          Key: MNG-17
>          URL: http://jira.codehaus.org/browse/MNG-17
>      Project: m2
>         Type: Improvement
>     Reporter: Trygve Laugstol

>
>
> For making it easier to implement the precontitions stated in the @parameter section of a plugin I'd like to make these changes:
> In the Plugin interface add:
>  validatingExecute( request, response );
> This method is assumed to validate the parameters of the plugin. This method makes is easier for maven or any third party to assume that the plugin validates it's parameters and it makes it easier for the plugin because it can assume that when it implements execute( param1, param2 ) the values of the parameters is valiated.
> The maven-plugin would need another generator that from a FooPlugin creates a subclass called ValidatingFooPlugin that takes the parameter definition and implements validatingExecute( .. ). The plugin.xml descriptor should use the Validating version of each plugin so maven too would get the validation for free.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org