Guillaume Nodet <******@****.***> 1664700085 +0200

  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.core.test</groupId>
  <artifactId>test-lifecycle-and-artifactHandler</artifactId>
  <packaging>jar</packaging>
  <version>1</version>
  <name>test-lifecycle-and-artifactHandler</name>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-assembly-plugin</artifactId>
        <version>2.2-beta-2-SNAPSHOT</version>

Guillaume Nodet <******@****.***> 1664700085 +0200

  provided both in terms of static expressions that are just looked up, and
  in terms of user-provided configuration from properties or the POM).
  If these mojos are to be first-class components, the configuration from these
  various sources must be consolidated and injected using the container.

  Currently, mojo configuration is done externally to the container, in the

  Notice that model interpolation happens <after> profile activation, and that profile activation doesn't benefit from every values:
  interpolation for file-based activation is limited to <<<$\{basedir}>>> (which was introduced in Maven 3 and is not deprecated
  in this context) and <<<$\{rootDirectory}>>> (introduced in Maven 4), system properties and user properties.

  Values are evaluated in sequence from different syntaxes:

~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2013-07-27
 -----

Maven Core

 Maven Core classes managing the whole build process.

* Reference Documentation

 * {{{./lifecycles.html}lifecycles}} and {{{./default-bindings.html}plugin bindings to <<<default>>> lifecycle}},

This directory contains Jansi native libraries extracted from Jansi JAR.

You can add your own build for platforms not natively supported by Jansi.
See here [1] on how to compile for your platform and here [2] how libraries
follow Jansi's directory and filename conventions.

[1] https://github.com/fusesource/jansi/tree/master/src/main/native

We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version.

<configuration>
  <lifecycles>
    <lifecycle>
      <id>default</id>
      <phases>
        <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>

Apache Maven is a software project management and comprehension tool. Based on
the concept of a project object model (POM), Maven can manage a project's
build, reporting and documentation from a central piece of information.

If you think you have found a bug, please file an issue in the [Maven Issue Tracker][jira].

Documentation

~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2012-09-29
 -----

Maven Artifact Resolver Provider

 Maven Artifact Resolver Provider is a {{{/resolver/}Maven Artifact Resolver}} extension to support
 Maven POMs and local+remote repositories.

 Main component is <<<MavenRepositorySystemUtils>>>