* specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.execution;

/**
 * Defines events that Maven fires during a build. <strong>Warning:</strong> This interface might be extended in future
 * Maven versions to support further events. Hence it is strongly recommended to derive custom listeners from
 * {@link AbstractExecutionListener} in order to avoid interoperability problems.
 *
 */

- check to see if anything is missing

    private boolean isProjectPresent = true;

    // ----------------------------------------------------------------------------
    // We need to allow per execution user and global settings as the embedder
    // might be running in a mode where it's executing many threads with totally
    // different settings.
    // ----------------------------------------------------------------------------

    private File userSettingsFile;

fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance("Foo"); into a single method call: Log log = LogFactory.getLog("Foo"); For example, you might use the following technique to initialize and use a Log instance in an application component: import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; public class MyComponent { protected static Log log = LogFactory.get...

        <field xdoc.separator="blank">
          <name>proxies</name>
          <version>1.0.0+</version>
          <description>
            Configuration for different proxy profiles. Multiple proxy profiles
            might come in handy for anyone working from a notebook or other
            mobile platform, to enable easy switching of entire proxy
            configurations by simply specifying the profile id, again either from

                        Version.V20,
                        prefix + "layout",
                        repository.getId(),
                        "uses the unsupported value 'legacy', artifact resolution might fail.",
                        repository);
            }
        }
    }

    private void validate20RawResources(

* Extension points that plugins might expose

h3. The plugin manager may have to deal with particular actions when a plugin is

* installation
* activation
* update
* deactivation
* un-installation

When a plugin is installed we may want to check the license and make users agree. We may also want to unpack the given plugin in a particular location.

    }

    private void assertVersionOlder(String left, String right) {
        assertTrue(
                newArtifactVersion(left).compareTo(newArtifactVersion(right)) < 0,
                left + " should be older than " + right);
        assertTrue(
                newArtifactVersion(right).compareTo(newArtifactVersion(left)) > 0,
                right + " should be newer than " + left);
    }

   | relies on the detection of a property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |

convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern: Log log = LogFactory.getFactory().getInstance(Foo.class); into a single method call: Log log = LogFactory.getLog(Foo.class); For example, you might use the following technique to initialize and use a Log instance in an application component: import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; public class MyComponent { protected static Log log = LogFactory.get...