replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

                        try {
                          echo "Checkout ITs from branch: ${ITS_BRANCH}"
                          checkout([$class: 'GitSCM',
                                  branches: [[name: ITS_BRANCH]],
                                  extensions: [[$class: 'CloneOption', depth: 1, noTags: true, shallow: true]],

LAUNCHER_JAR=`echo "$MAVEN_HOME"/boot/plexus-classworlds-*.jar`

    (June 1995), all U.S. Government End Users acquire Covered Software
    with only those rights set forth herein. This U.S. Government Rights
    clause is in lieu of, and supersedes, any other FAR, DFAR, or other
    clause or provision that addresses Government rights in computer
    software under this License.

9. MISCELLANEOUS.

    This License represents the complete agreement concerning subject

Copyright (c) 2002-2024, the original author or authors.
All rights reserved.

https://opensource.org/licenses/BSD-3-Clause

Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

 ---

Legacy Artifact Handlers Reference

  Maven 3 artifact handlers (see {{{../maven-artifact/apidocs/org/apache/maven/artifact/handler/ArtifactHandler.html} API}})
  define for each {{{../maven-model/maven.html#class_dependency}dependency type}} information on the artifact
  (classifier, extension, language) and how to manage it as dependency (add to classpath, include dependencies).

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

~~ 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

  "-Dclassworlds.conf=$CLASSWORLDS_CONF" \
  "-Dmaven.home=$MAVEN_HOME" \
  "-Dlibrary.jansi.path=${MAVEN_HOME}/lib/jansi-native" \
  "-Dmaven.multiModuleProjectDirectory=$MAVEN_PROJECTBASEDIR" \
  $LAUNCHER_CLASS \
  $MAVEN_ARGS \

                                  echo "Checkout ITs from branch: ${ITS_BRANCH}"
                                  checkout([$class: 'GitSCM',
                                          branches: [[name: ITS_BRANCH]],
                                          extensions: [[$class: 'CloneOption', depth: 1, noTags: true, shallow: true]],