:init

set "CLASSWORLDS_CONF=%MAVEN_HOME%\bin\m2.conf"

@REM Find the project basedir, i.e., the directory that contains the directory ".mvn".
@REM Fallback to current working directory if not found.

set "EXEC_DIR=%CD%"
set "WDIR=%EXEC_DIR%"

@REM Look for the --file switch and start the search for the .mvn directory from the specified
@REM POM location, if supplied.

set FILE_ARG=
:arg_loop
if "%~1" == "-f" (
  set "FILE_ARG=%~2"

    $ mvn dbflute:download # (one time command)
    $ mvn dbflute:freegen
    $ mvn license:format

### Test d'integration

Lancer le serveur Fess et éxécuter la commande suivante :

    $ mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201"

Pour exécuter un seul cas de test case, vous pouvez utiliser la commande suivante :

        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
        restore-keys: |
          ${{ runner.os }}-maven-
    - name: Download Plugins with Maven
      run: mvn -B antrun:run --file pom.xml
    - name: Build with Maven
      run: mvn -B source:jar javadoc:jar package --file pom.xml
    - name: Run Fess
      run: bash src/test/resources/before_script.sh
    - name: Run Integration Test

    $ mvn dbflute:freegen
    $ mvn license:format

### Integration Tests

Launch Fess Server and run the following command:

    $ mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201"

To run a single test case, you can use:

 *
 * The default implementation will look for a {@code .mvn} child directory
 * or a {@code pom.xml} containing the {@code root="true"} attribute.
 */
public interface RootLocator {

    String UNABLE_TO_FIND_ROOT_PROJECT_MESSAGE = "Unable to find the root directory. "
            + "Create a .mvn directory in the root directory or add the root=\"true\""

                + "      mvn install:install-file -DgroupId=aGroupId -DartifactId=anArtifactId -Dversion=aVersion "
                + "-Dclassifier=aClassifier -Dpackaging=jar -Dfile=/path/to/file" + LS + LS
                + "  Alternatively, if you host your own repository you can deploy the file there: " + LS
                + "      mvn deploy:deploy-file -DgroupId=aGroupId -DartifactId=anArtifactId"

        <include>**</include>
      </includes>
    </fileSet>
	<fileSet>
      <directory>src/assembly/maven/bin</directory>
      <outputDirectory>bin</outputDirectory>
      <includes>
        <include>mvn</include>
        <include>mvnDebug</include>
        <!-- This is so that CI systems can periodically run the profiler -->
        <include>mvnyjp</include>
      </includes>
      <lineEnding>unix</lineEnding>

        env:
          TAR_BALL: apache-maven/target/apache-maven-bin.tar.gz

      - name: Clean with Maven
        run: mvn clean

      - name: Build again with Maven SNAPSHOT
        shell: bash
        run: |
          set +e
          export PATH=${{ env.TEMP_MAVEN_BIN_DIR }}:$PATH

## Develop and verify

After you make a change, you can run `mvn clean teamcity-configs:generate` to generate and verify the generated TeamCity configuration XMLs.

You also need to run `mvn clean verify` with Java 8 before committing changes.

If you have ktlint errors, you can automatically fix them by running `mvn com.github.gantsign.maven:ktlint-maven-plugin:1.1.1:format`.

## How the configuration works

        with:
          path: maven/
          persist-credentials: false

      - name: Build Maven
        run: mvn install -e -B -V -DdistributionFileName=apache-maven -DskipTests -f maven/pom.xml

      - name: Running integration tests
        shell: bash
        run: mvn install -e -B -V -Prun-its,embedded -DmavenDistro="$GITHUB_WORKSPACE/maven/apache-maven/target/apache-maven-bin.zip" -f maven-integration-testing/pom.xml