<phase>package</phase>
      <implementation>org.apache.maven.plugin.jar.JarMojo</implementation>
      <language>java</language>
      <instantiationStrategy>per-lookup</instantiationStrategy>
      <executionStrategy>once-per-session</executionStrategy>
      <deprecated>deprecated-mojo</deprecated>
      <since>2.2</since>
      <executePhase>generate-sources</executePhase>
      <executeGoal>some-goal</executeGoal>

 * under the License.
 */
package org.apache.maven.cli.logging;

/**
 * Interface for configuration operations on loggers, which are not available in slf4j, then require per-slf4f-binding
 * implementation.
 *
 * @since 3.1.0
 */
public interface Slf4jConfiguration {
    /**
     * Level
     */
    enum Level {
        DEBUG,
        INFO,
        ERROR
    }

/**
 * Basher test for {@link ConcurrentHashMultiset}: start a bunch of threads, have each of them do
 * operations at random. Each thread keeps track of the per-key deltas that it's directly
 * responsible for; after all threads have completed, we sum the per-key deltas and compare to the
 * existing multiset values.
 *
 * @author mike nonemacher
 */

public class ConcurrentHashMultisetBasherTest extends TestCase {

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.repository.legacy;

import javax.inject.Named;

/**
 * Wagon with per-lookup instantiation strategy.
 */
@Named("perlookup")
public class PerLookupWagon extends WagonMock {

    public String[] getSupportedProtocols() {
        return new String[] {"perlookup"};
    }

    <component>
      <role>org.apache.maven.wagon.Wagon</role>
      <role-hint>testfile</role-hint>
      <implementation>org.apache.maven.artifact.resolver.TestFileWagon</implementation>
      <instantiation-strategy>per-lookup</instantiation-strategy>
    </component>
  </components>

* References

 * {{{./cli.html}CLI options}},

 * {{{./logging.html}logging API}}.

 * since 3.3.1 (see {{{/docs/3.3.1/release-notes.html#Core_Extensions}3.3.1 release notes}} for more details),
   per project settings can be defined by files in <<<.mvn/>>> directory:

   * <<<.mvn/jvm.config>>> containing jvm options,

   * <<<.mvn/maven.config>>> containing Maven command-line parameter,

Let's imagine that you have some **machine learning models** that you want to use to handle requests. 🤖

The same models are shared among requests, so, it's not one model per request, or one per user or something similar.

Let's imagine that loading the model can **take quite some time**, because it has to read a lot of **data from disk**. So you don't want to do it for every request.

        repository.</description>
      <cliOptions>
        <cliOption>
          <key>-Dmaven.repo.local=/path/to/local/repo</key>
          <value>Override the local repository location on a per-build basis.</value>
        </cliOption>
      </cliOptions>
    </expression>
    <expression>
      <syntax>reactorProjects</syntax>
      <description>This is the current list of projects being built by

    public static final String MAVEN_PLUGIN = "maven-plugin";

    /** "once-per-session" execution strategy */
    public static final String SINGLE_PASS_EXEC_STRATEGY = "once-per-session";

    /** "always" execution strategy */
    public static final String MULTI_PASS_EXEC_STRATEGY = "always";

    private static final String DEFAULT_INSTANTIATION_STRATEGY = "per-lookup";

    private static final String DEFAULT_LANGUAGE = "java";

      <description>
        <![CDATA[
      Flags the system as offline, to prevent accessing the network to resolve artifacts or execute plugins.

      NOTE: It's also possible to switch to offline mode on a per-build basis, using the '-o' command-line option.
    ]]></description>
    </expression>
    <expression>
      <syntax>settings.interactiveMode</syntax>
      <configuration>
        <![CDATA[