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

 -----
 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>>>
 ({{{./apidocs/org/apache/maven/repository/internal/MavenRepositorySystemUtils.html}javadoc}},
 {{{./xref/org/apache/maven/repository/internal/MavenRepositorySystemUtils.html}source}}).

        <remoteArtifactRepositories implementation="java.util.List">${project.remoteArtifactRepositories}</remoteArtifactRepositories>
        <appendedResourcesDirectory implementation="java.io.File">${basedir}/src/main/appended-resources</appendedResourcesDirectory>
        <excludeScope implementation="java.lang.String" default-value="">${excludeScope}</excludeScope>

quarkus/test-framework/kubernetes-client/pom.xml
	quarkus/test-framework/common/pom.xml
quarkus/independent-projects/arc/processor/pom.xml
	quarkus/independent-projects/arc/runtime/pom.xml
quarkus/integration-tests/main/pom.xml
	quarkus/integration-tests/class-transformer/runtime/pom.xml
	quarkus/integration-tests/shared-library/pom.xml
	quarkus/extensions/micrometer/runtime/pom.xml
	quarkus/extensions/smallrye-openapi/runtime/pom.xml

%{snippet|id=default|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/DefaultLifecycleProvider.java}

* <<<clean>>> Lifecycle

  <<<clean>>> lifecycle phases are defined with their plugins bindings:

%{snippet|id=clean|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/CleanLifecycleProvider.java}

* <<<site>>> Lifecycle

+ Fork the repository on GitHub.

Making and Submitting Changes
--------------

We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the
main channel of communication for contributors.  
There are some guidelines which will make applying PRs easier for us:
+ Create a topic branch from where you want to base your work (this is usually the master branch).

  </organization>
  <build>
    <sourceDirectory>src/main/java</sourceDirectory>
    <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory>
    <testSourceDirectory>src/test/java</testSourceDirectory>
    <outputDirectory>target/classes</outputDirectory>
    <testOutputDirectory>target/test-classes</testOutputDirectory>
    <resources>
      <resource>
        <directory>src/main/resources</directory>
      </resource>

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2013-03-19
 -----

Maven Model Builder

 The effective model builder, with profile activation, inheritance, interpolation, ...

 The main component is <<<ModelBuilder>>>
 ({{{./apidocs/org/apache/maven/model/building/ModelBuilder.html}javadoc}},
 {{{./xref/org/apache/maven/model/building/ModelBuilder.html}source}}),
 with its <<<DefaultModelBuilder>>> implementation

%{snippet|id=jar|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/JarLifecycleMappingProvider.java}

* Plugin bindings for <<<ejb>>> packaging

%{snippet|id=ejb|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/EjbLifecycleMappingProvider.java}

* Plugin bindings for <<<maven-plugin>>> packaging

 ---

Maven Core Extensions Reference

  Maven core provides default {{{./extension.html}extensions}} as defined in <<</META-INF/maven/extension.xml>>>: