testing/precondition-tester                 @gradle/bt-developer-productivity

# Release coordination
packaging/core-platform/                        @gradle/bt-product-operations
packaging/distributions-dependencies/           @gradle/bt-product-operations
packaging/distributions-full/                   @gradle/bt-product-operations
packaging/public-api                            @gradle/bt-product-operations

                    <groupId>com.example</groupId>
                    <artifactId>parent-project</artifactId>
                    <version>1.0.0</version>
                    <packaging>pom</packaging>
                </project>
                """;

            // Create child POM that references the parent
            String childPomXml = """
                <?xml version="1.0" encoding="UTF-8"?>

        boolean flattenEnabled = Features.consumerPomFlatten(session.getConfigProperties());
        String packaging = model.getPackaging();
        String originalPackaging = project.getOriginalModel().getPackaging();

        // Check if this is a BOM (original packaging is "bom")
        boolean isBom = BOM_PACKAGING.equals(originalPackaging);

        // Check if mixins are present without flattening enabled

            <option value="$PROJECT_DIR$/packaging/distributions-full" />
            <option value="$PROJECT_DIR$/packaging/internal-build-reports" />
            <option value="$PROJECT_DIR$/packaging/public-api" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/api-metadata" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/base-diagnostics" />

    /**
     * {@return the project version}.
     */
    @Nonnull
    String getVersion();

    /**
     * {@return the project packaging}.
     * <p>
     * Note: unlike in legacy code, logical checks against string representing packaging (returned by this method)
     * are NOT recommended (code like {@code "pom".equals(project.getPackaging)} must be avoided). Use method

that use custom task names. These are usually found in "qa" projects commonly
use the "integTest" task.

If in doubt about which command to use, simply run <gradle path>:check

== Testing packaging

The packaging tests use Vagrant virtual machines or cloud instances to verify
that installing and running Elasticsearch distributions works correctly on
supported operating systems. These tests should really only be run on ephemeral

    "path": "platforms/core-execution/build-cache-local",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "build-cache-packaging",
    "path": "platforms/core-execution/build-cache-packaging",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "build-cache-spi",

h4. Generation of plugin metadata and packaging

To create the packaging for a plugin a special Maven packaging would be created with an accompanying life-cycle in order to create the plugin metadata required and create an archive of the plugin that can be consumed at runtime.

  <parent>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>apache-maven</artifactId>
  <packaging>pom</packaging>

  <name>Apache Maven Distribution</name>
  <description>The Apache Maven distribution, source and binary, in zip and tar.gz formats.</description>

  <dependencies>
    <dependency>

  <parent>
    <groupId>com.google.guava</groupId>
    <artifactId>guava-parent</artifactId>
    <version>999.0.0-HEAD-android-SNAPSHOT</version>
  </parent>
  <artifactId>guava</artifactId>
  <packaging>bundle</packaging>
  <name>Guava: Google Core Libraries for Java</name>
  <description>
    Guava is a suite of core and expanded libraries that include
    utility classes, Google's collections, I/O classes, and
    much more.