// <plugin/> block in a Maven POM. We have to do some wiggling to pull the sources of information
    // together and this really shows the problem of constructing a sensible default configuration, but
    // it's all encapsulated here so it appears normalized to the POM builder.

    // We are going to take the project packaging and find all plugin in the default lifecycle and create

        <version>0.2</version>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>test</groupId>
        <artifactId>g</artifactId>
        <version>1</version>
        <type>pom</type>
        <scope>include</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

Guillaume Nodet <******@****.***> 1729859506 +0200

under the License.
-->

<project>
    <modelVersion>4.0.0</modelVersion>
    <artifactId>aid</artifactId>
    <groupId>gid</groupId>
    <version>0.1</version>
    <packaging>pom</packaging>

    <profiles>
        <profile>
            <id>+invalid-id</id>
        </profile>
        <profile>
            <id>-invalid-id</id>
        </profile>
        <profile>

 *
 * @see org.apache.maven.execution.MavenSession
 */
public interface Maven {
    @Deprecated
    @SuppressWarnings("checkstyle:constantname")
    String POMv4 = "pom.xml";

    MavenExecutionResult execute(MavenExecutionRequest request);

    public int hashCode() {
        return 10 + getId().hashCode();
    }

    public MojoDescriptor getMojo(String goal) {
        if (getMojos() == null) {
            return null; // no mojo in this POM
        }

        // TODO could we use a map? Maybe if the parent did that for components too, as this is too vulnerable to
        // changes above not being propagated to the map

            "project",
            "reactorProjects",
            "session",
            "settings");

    private static final List<String> IGNORED_PROPERTY_PREFIX =
            Arrays.asList("mojo.", "pom.", "plugin.", "project.", "session.", "settings.");

    protected AbstractMavenPluginDescriptorSourcedParametersValidator(PluginValidationManager pluginValidationManager) {
        super(pluginValidationManager);
    }

                if (r.getEffectiveModel() != null) {
                    File pom = r.getSource().getPath().toFile();
                    MavenProject project =
                            projectIndex.get(r.getEffectiveModel().getId());
                    Path rootDirectory =
                            rootLocator.findRoot(pom.getParentFile().toPath());
                    project.setRootDirectory(rootDirectory);

Guillaume Nodet <******@****.***> 1729859506 +0200

     * {@return the type of the dependency}
     * A dependency can be a <abbr>JAR</abbr> file,
     * a modular-<abbr>JAR</abbr> if it is intended to be placed on the module path,
     * a <abbr>JAR</abbr> containing test classes, a POM file, <i>etc.</i>
     */
    @Nonnull
    Type getType();

    /**
     * {@return the time at which the dependency will be used}
     * It may be, for example, at compile time only, at run time, or at test time.