* <p>
 * Example usage:
 * <pre>
 * public class CustomProjectScopeProvider implements ProjectScopeProvider {
 *     public Collection&lt;ProjectScope&gt; provides() {
 *         return Collections.singleton(projectScope("integration-test"));
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.ProjectScope
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider
 * @since 4.0.0
 */
@Experimental
@Consumer
@Named

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng3822</groupId>
  <artifactId>test1</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3822</name>
  <description>
    Verify that POM interpolation uses basedir-aligned build directories.
  </description>

  <properties>

lasta_di.smart.deploy.mode = warm

# Is development environment here? (used for various purpose, you should set false if unknown)
development.here = true

# The title of environment (e.g. local or integration or production)
environment.title = Local Development

# Does it enable the Framework internal debug? (true only when emergency)
framework.debug = false

-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its</groupId>
  <artifactId>b</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: Dummy Artifact</name>
  <description>

  </description>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>

  <parent>
    <groupId>org.apache.maven.its.mng3023</groupId>
    <artifactId>parent</artifactId>
    <version>1</version>
  </parent>

  <artifactId>consumer</artifactId>

  <name>Maven Integration Test :: MNG-3023 :: Consumer</name>
  <description>Test that reactor projects are included in dependency resolution.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven.its.mng3023</groupId>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-install-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>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-resources-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>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>

    }

    /**
     * multiModuleProjectDirectory in MavenExecutionRequest is not always the parent of the request pom.
     * We should always check whether the request pom project is collected.
     * The integration tests for MNG-6223 are examples for this scenario.
     *
     * @return true if the collected projects contain the requested project (for example with -f)
     */

* **Aucun compromis** avec les bases de données, les frontends, etc. Mais une intégration facile avec n'importe lequel d'entre eux.

### "Plug-ins" illimités

Ou, en d'autres termes, pas besoin d'eux, importez le code que vous voulez et utilisez le.

        void testDeprecatedAnnotation() {
            // Then
            assertTrue(Handler.class.isAnnotationPresent(Deprecated.class));
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should support NTLM over HTTPS")
        void testNtlmSupport() {
            // When