**/target/**
.project
.classpath
.settings/
.svn/
# Intellij
*.ipr
*.iml
.idea
.DS_Store
/bootstrap
/dependencies.xml
.java-version
.checkstyle
.factorypath
.vscode/
repo/

  <modelVersion>4.0.0</modelVersion>

  <!-- Shared parent. Doesn't define a lot of things about Apache like general mailing lists, but does
       define the settings common to all projects at Apache -->
  <groupId>org.apache</groupId>
  <artifactId>apache</artifactId>
  <version>3</version>
  <packaging>pom</packaging>
  <name>The Apache Software Foundation</name>
  <description>

** Accessibility of offline status

  Offline status should be indicated in the MavenSettings instance, since it
  can conceivably be set from either the settings.xml or the command-line.

  In the event the '-o' switch is the impetus for setting offline mode, this
  should result in modification of the active profile in the MavenSettings
  instance, just as definition of the active profile from the command-line

  <modelVersion>4.0.0</modelVersion>

  <!-- Shared parent. Doesn't define a lot of things about Apache like general mailing lists, but does
       define the settings common to all projects at Apache -->
  <groupId>org.apache</groupId>
  <artifactId>apache</artifactId>
  <version>1</version>
  <packaging>pom</packaging>
  <name>The Apache Software Foundation</name>
  <description>

 -----

Maven 4 API - Immutable Settings Model

 This is strictly the immutable model for Maven settings in <<<org.apache.maven.api.settings>>> package.

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with <<<Builder>>> inner classes for immutable instances creation.

 See also corresponding {{{../../maven-settings/index.html}Maven classical settings model documentation}}.

    <module>maven-profile</module>
    <module>maven-project</module>
    <module>maven-reporting</module>
    <module>maven-repository-metadata</module>
    <module>maven-script</module>
    <module>maven-settings</module>
  </modules>
  <repositories>
    <repository>
      <releases>
        <enabled>false</enabled>
      </releases>
      <id>snapshots</id>
      <name>Maven Central Development Repository</name>

 that belong to the same group, the project level allows configuration management at
 the project level, and the user level allows users to override settings on
 the site level, group level and project level.

* Site configuration

 At the site level all configuration is achieved by tweaking the various files that

~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ 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