maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-17) Improve the validation of mojo parameters
Date Sat, 12 Mar 2005 18:25:32 GMT
     [ http://jira.codehaus.org/browse/MNG-17?page=history ]

Brett Porter updated MNG-17:
----------------------------

    Fix Version:     (was: 1.0-alpha-1)
                 1.0-alpha-2
        Version:     (was: 1.0-alpha-1)
    Environment: 
    Description: 
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.

  was:
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.


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

>
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message