@Test
    void testBuilderCommon() {
        List<String> msgs = new ArrayList<>();
        msgs.add("*****************************************************************");
        msgs.add("* Your build is requesting parallel execution, but project      *");
        msgs.add("* contains the following plugin(s) that have goals not marked   *");
        msgs.add("* as @threadSafe to support parallel building.                  *");

              <version>1.1.0</version>
              <models>
                <model>src/main/mdo/remote-resources.mdo</model>
              </models>
            </configuration>
          </execution>
          <execution>
            <id>supplemental-models</id>
            <goals>
              <goal>xpp3-writer</goal>
              <goal>java</goal>
              <goal>xpp3-reader</goal>
            </goals>

 * under the License.
 */
package org.apache.maven.execution.scope.internal;

import java.util.Collection;
import java.util.IdentityHashMap;

import com.google.inject.Key;
import com.google.inject.Provider;
import com.google.inject.Scope;
import com.google.inject.name.Named;
import org.apache.maven.execution.MojoExecutionEvent;
import org.apache.maven.execution.MojoExecutionListener;

These dependencies will be executed/solved the same way as normal dependencies. But their value (if they return any) won't be passed to your *path operation function*.

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

 * under the License.
 */
package org.apache.maven.lifecycle.internal;

import org.apache.maven.execution.ExecutionEvent;
import org.apache.maven.execution.MavenSession;
import org.apache.maven.plugin.MojoExecution;

/**
 * Assists in firing execution events. <strong>Warning:</strong> This is an internal utility interface that is only

O arquivo `test_main.py` teria os testes para para o arquivo `main.py`, ele poderia ficar assim:

{* ../../docs_src/async_tests/app_a_py39/test_main.py *}

## Executá-lo { #run-it }

Você pode executar os seus testes normalmente via:

<div class="termy">

```console
$ pytest

---> 100%
```

</div>

## Em Detalhes { #in-detail }

 * under the License.
 */
package org.apache.maven.eventspy.internal;

import org.apache.maven.execution.AbstractExecutionListener;
import org.apache.maven.execution.ExecutionEvent;
import org.apache.maven.execution.ExecutionListener;

/**
 * Forwards execution events to EventSpies.
 * @since 3.0.2
 */
class EventSpyExecutionListener extends AbstractExecutionListener {

 * Exception thrown when an error occurs during Maven execution.
 * This exception wraps the original cause of the execution failure.
 *
 * @since 4.0.0
 */
@Experimental
public class MavenExecutionException extends MavenException {

    /**
     * Constructs a new MavenExecutionException with the specified cause.
     *
     * @param cause The underlying exception that caused the execution failure
     */

          </configuration>
          <executions>
            <execution>
              <id>site-docs</id>
              <phase>pre-site</phase>
              <goals>
                <goal>xdoc</goal>
                <goal>xsd</goal>
              </goals>
            </execution>
            <execution>
              <id>standard</id>
              <goals>
                <goal>java</goal>

    }
}

dependencies {
    integTestRuntimeOnly(project(":kotlin-dsl-plugins")) {
        because("Tests require 'future-plugin-versions.properties' on the test classpath and the embedded executer needs them available")
        attributes {
            attribute(LibraryElements.LIBRARY_ELEMENTS_ATTRIBUTE, objects.named("future-versions-resource"))
        }
    }