You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2004/06/27 18:41:28 UTC
[jira] Created: (MNG-17) Improve the validation of mojo parameters
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-17
Summary: Improve the validation of mojo parameters
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Assignee:
Reporter: Trygve Laugstol
Created: Sun, 27 Jun 2004 12:40 PM
Updated: Sun, 27 Jun 2004 12:40 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MNG-17) Improve the validation of mojo parameters
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 27 Jan 2005 2:01 AM
Changes:
Fix Version changed from 1.0-alpha-2
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-17?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-17
Summary: Improve the validation of mojo parameters
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Assignee:
Reporter: Trygve Laugstol
Created: Sun, 27 Jun 2004 12:40 PM
Updated: Thu, 27 Jan 2005 2:01 AM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MNG-17) Improve the validation of mojo parameters
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-17) Improve the validation of mojo parameters
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 27 Jan 2005 4:41 PM
Changes:
Version changed to 1.0-alpha-1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-17?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-17
Summary: Improve the validation of mojo parameters
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Fix Fors:
1.0-alpha-1
Versions:
1.0-alpha-1
Assignee:
Reporter: Trygve Laugstol
Created: Sun, 27 Jun 2004 12:40 PM
Updated: Thu, 27 Jan 2005 4:41 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MNG-17) Improve the validation of mojo parameters
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 22 Jul 2004 2:49 PM
Changes:
Fix Version changed to 1.0-alpha-2
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-17?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-17
Summary: Improve the validation of mojo parameters
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Fix Fors:
1.0-alpha-2
Assignee:
Reporter: Trygve Laugstol
Created: Sun, 27 Jun 2004 12:40 PM
Updated: Thu, 22 Jul 2004 2:49 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
[jira] Updated: (MNG-17) Improve the validation of mojo parameters
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 27 Jan 2005 4:41 PM
Changes:
Fix Version changed to 1.0-alpha-1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-17?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-17
Summary: Improve the validation of mojo parameters
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Fix Fors:
1.0-alpha-1
Assignee:
Reporter: Trygve Laugstol
Created: Sun, 27 Jun 2004 12:40 PM
Updated: Thu, 27 Jan 2005 4:41 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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