</executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>create-distribution-in-dir</id>
      <activation>
        <property>
          <name>distributionTargetDir</name>
        </property>
      </activation>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-from-pluginManagement-plugin</artifactId>
          <version>1.0</version>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>
      <plugin>
        <artifactId>maven-from-plugins-plugin</artifactId>
        <version>1.0</version>
      </plugin>
    </plugins>
  </build>

  <reporting>
    <plugins>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>2.1</version>
          <configuration>
            <source>  1.5  </source>
            <target xml:space="preserve">  1.5  </target>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>

					"platform-jvm",
					"plugin-development",
					"plugin-use",
					"plugins-application",
					"plugins-distribution",
					"plugins-groovy",
					"plugins-java-base",
					"plugins-java-library",
					"plugins-jvm-test-fixtures",
					"plugins-jvm-test-suite",
					"plugins-test-report-aggregation",
					"plugins-version-catalog",
					"precondition-tester",
					"problems",
					"problems-api",

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven</groupId>
  <artifactId>p0</artifactId>
  <packaging>pom</packaging>
  <version>1.0</version>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <executions>
          <execution>
            <id>test</id>

            <!--  The key to this test... -->

              <phase>none</phase>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <profile>
      <id>reporting</id>
      <reporting>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
            <configuration>
              <tags>

include("module-identity")

// Code quality rules common to :build-logic and the root build
include("code-quality-rules")

// Plugins to build :build-logic plugins
include("gradle-plugin")

// Plugins to publish gradle projects
include("publishing")

rootProject.name = "build-logic-commons"

// Make sure all the build-logic is compiled for the right Java version

- we have to deal with scripting implementations (groovy, beanshell, ruby)
- we need to deal with a shared context for plugins, like the guarded mojos
- we need to deal with plugins as core application logic which can also interact with plugins

* Along with this comes the testing strategies that make this work
* The repository model where plugins can be stored and cataloged
* Bridging this into an OSGi system: if this could be done then we can basically take over p2

      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-params</artifactId>
      <scope>test</scope>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <configuration>
          <archive>
            <manifestEntries>

          <overrides>
            <parent-only>parent</parent-only>
            <parent>parent</parent>
          </overrides>
        </configuration>
      </plugin>
    </plugins>
  </build>

  <reporting>
    <plugins>
      <plugin>
        <artifactId>MNG-5115</artifactId>
        <reportSets>
          <reportSet>
            <id>default-inherited</id>
            <reports>