* This is the main trigger for the <code>Mojo</code> inside the <code>Maven</code> system, and allows
     * the <code>Mojo</code> to communicate errors.
     *
     * @throws MojoException if a problem occurs
     */
    void execute();

@Target(ElementType.TYPE)
@Inherited
public @interface Mojo {
    /**
     * goal name (required).
     * @return the goal name
     */
    @Nonnull
    String name();

    /**
     * default phase to bind your mojo.
     * @return the default phase
     */
    @Nonnull
    String defaultPhase() default "";

    /**
     * does your mojo requires a project to be executed?
     * @return requires a project

                ((ContextEnabled) mojo).setPluginContext(pluginContext);
            }
        }

        if (mojo instanceof Mojo) {
            Logger mojoLogger = LoggerFactory.getLogger(mojoDescriptor.getImplementation());
            ((Mojo) mojo).setLog(new MojoLogWrapper(mojoLogger));
        }

        if (mojo instanceof Contextualizable) {

    private final Mojo mojo;

    private final Throwable cause;

    public MojoExecutionEvent(MavenSession session, MavenProject project, MojoExecution mojoExecution, Mojo mojo) {
        this(session, project, mojoExecution, mojo, null);
    }

    public MojoExecutionEvent(
            MavenSession session, MavenProject project, MojoExecution mojoExecution, Mojo mojo, Throwable cause) {

    /**
     * Looks up the mojo for the specified mojo execution and populates its parameters from the configuration given by
     * the mojo execution. The mojo/plugin descriptor associated with the mojo execution provides the class realm to
     * look up the mojo from. <strong>Warning:</strong> The returned mojo instance must be released via

~~ under the License.

  ---
  Getting to Plexus-configured Mojos
  ---
  John Casey
  ---
  2005-04-29

Abstract

  We're moving toward integrating mojos as first-class plexus components, while
  at the same time avoiding introducing required plexus dependencies into the
  mojo development model.

  In order to really achieve this, we need mojo configurations (which are

        List<LifecycleMojo> mojos = goals.getMojos();
        if (mojos != null) {
            for (int i = 0; i < mojos.size(); i++) {
                LifecycleMojo mojo = mojos.get(i);

                // Compute goal coordinates
                String groupId, artifactId, version, goal;
                String[] p = mojo.getGoal().trim().split(":");
                if (p.length == 3) {

          <description>
            The goal name for the Mojo, that users will reference from the command line to execute the Mojo directly,
            or inside a POM in order to provide Mojo-specific configuration.
          </description>
        </field>
        <field>
          <name>description</name>
          <version>1.0.0+</version>
          <type>String</type>

                    String str = ownerMojo != null ? " The " + ownerMojo.getId() : "An";
                    String msg = str + " aggregator mojo is already being executed "
                            + "in this parallel build, those kind of mojos require exclusive access to "
                            + "reactor to prevent race conditions. This mojo execution will be blocked "

public enum EventType {
    PROJECT_DISCOVERY_STARTED,
    SESSION_STARTED,
    SESSION_ENDED,
    PROJECT_SKIPPED,
    PROJECT_STARTED,
    PROJECT_SUCCEEDED,
    PROJECT_FAILED,
    MOJO_SKIPPED,
    MOJO_STARTED,
    MOJO_SUCCEEDED,
    MOJO_FAILED,
    FORK_STARTED,
    FORK_SUCCEEDED,
    FORK_FAILED,
    FORKED_PROJECT_STARTED,
    FORKED_PROJECT_SUCCEEDED,
    FORKED_PROJECT_FAILED,