bool reset_context, int keep_alive_secs,
                                      int64_t init_timeout_in_ms, int retries,
                                      bool clear_existing_contexts = false) = 0;

  // Initializes context for the local worker and no contexts will be created
  // for remote workers. Currently this only works for resetting context.

META-INF/MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: BEBE Build-Jdk: 1.6.0_07 META-INF/maven/plugin.xml A test plugin to assist testing of Maven core. org.apache.maven.plugins maven-clean-plugin 0.1 clean false true clean Does nothing. false true false false false true org.apache.maven.plugin.coreit.ItMojo java per-lookup once-per-session org.apache.maven maven-plugin-api jar 2.0 org/apache/maven/plugin/coreit/ItMojo.class package org.apache.maven.plugin.coreit;...

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-clean-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>

          else
            echo "${{ env.TAR_BALL }} does not exist."
            exit 1;
          fi
        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

 * #iterator()} method after the first, and whose iterator is always unmodifiable.
 *
 * <p>The {@code Iterable} specification does not make it absolutely clear what should happen on a
 * second invocation, so implementors have made various choices, including:
 *
 * <ul>
 *   <li>returning the same iterator again
 *   <li>throwing an exception of some kind

 * #iterator()} method after the first, and whose iterator is always unmodifiable.
 *
 * <p>The {@code Iterable} specification does not make it absolutely clear what should happen on a
 * second invocation, so implementors have made various choices, including:
 *
 * <ul>
 *   <li>returning the same iterator again
 *   <li>throwing an exception of some kind

    #   make release

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v3
      with:
        config-file: ./.github/codeql/codeql-config.yml

    - name: Cleanup Gradle Cache
      # Cleans up the Gradle caches before being cached
      run: |
        rm -f ~/.gradle/caches/modules-2/modules-2.lock
        rm -f ~/.gradle/caches/modules-2/gc.properties

func (j *xlMetaV2Version) unmarshalV(v uint8, bts []byte) (o []byte, err error) {
	if v > xlMetaVersion {
		return bts, fmt.Errorf("unknown xlMetaVersion: %d", v)
	}

	// Clear omitempty fields:
	if j.ObjectV2 != nil && len(j.ObjectV2.PartIndices) > 0 {
		j.ObjectV2.PartIndices = j.ObjectV2.PartIndices[:0]
	}
	o, err = j.UnmarshalMsg(bts)

        list.clear();
        authenticator.addGroupOrRoleName(list, "test", true);
        assertEquals(1, list.size());
        assertEquals("test", list.get(0));

        list.clear();
        authenticator.addGroupOrRoleName(list, "test", false);
        assertEquals(1, list.size());
        assertEquals("test", list.get(0));

        list.clear();

The [Map.Clear] method deletes all the entries, resulting in