On 10/6/05, Allison, Bob <[EMAIL PROTECTED]> wrote: > What is the criteria for a mojo class? In other words, when I define a > bunch of classes in a project with packaging of "maven-plugin", how is > it determined which of those classes are mojos and which are other > things?
I'd have said "implements Mojo" but apparently not :) for Java, it is any class with class level javadoc containing a @goal tag. See JavaMojoDescriptorExtractor. > What is the difference between MojoExecutionException and > MojoFailureException? They have the same documentation but I assume > that they should be used for different types of problems. Should result in a BUILD ERROR or BUILD FAILURE respectively. MEE has a causing exception, while the other is just a string. MEE should be the "unexpected" one, while MFE is more "expected" failures (like compilation errors). This is new and a lot of the plugins don't deal with it well. > When defining parameters to a mojo, I see that some mojos include a > setter for the parameter but a lot do not have any setter. Is there > some criteria to be used to determine when a setter is needed or > desired? If it is there, it is used. If not, private field injection is used. > What types of objects can be used as parameters? I assume this has > something to do with what plexus can convert from XML content. http://svn.plexus.codehaus.org/trunk/plexus-containers/plexus-container-default/src/main/java/org/codehaus/plexus/component/configurator/converters/ - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
