You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/05/04 22:24:20 UTC

[jira] Commented: (MNG-275) design and publish the Mojo API

     [ http://jira.codehaus.org/browse/MNG-275?page=comments#action_38536 ]
     
John Casey commented on MNG-275:
--------------------------------

If we allow simple specification of the execute() method to be sufficient for a mojo to be a mojo (plus metadata of course), then what are the implications for the throws clause of this method? Will we be forced back into "throws Exception" or will we dictate that if the method throws anything, it must throw MojoExecutionException or a derivative of RuntimeException?

I'd probably be +1 for the latter, which is to say that we check the throws clause reflectively, and if we detect a throws clause that isn't limited to derivatives of RuntimeException or MojoExecutionException, we error out and yell at the user...I'm really not in favor of hoping that mojo developers aren't just passing exception on through the system sans interpretation, and this will be the case if we allow "throws Exception". There needs to be enough of an inconvenience to the mojo developer to think about what [s]he is doing...

> design and publish the Mojo API
> -------------------------------
>
>          Key: MNG-275
>          URL: http://jira.codehaus.org/browse/MNG-275
>      Project: m2
>         Type: Task
>   Components: design
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 2.0-alpha-2

>
>
> we need to solidify the Mojo API so that others can start writing them with confidence.
> This includes:
> - strategy for dealing with types
> - dealing with responses
> - reviewing logging and events
> - considering whether extending a class is too cumbersome
> - what basic types we might want to provide without going overboard
> anything else?

-- 
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