<name>Model inheritance test parent: module directory != artifactId</name>
  <description>
    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"
    feature: support "project.directory" property, ressembling future model addition of "directory" element along "artifactId"
  </description>

  <properties>
    <project.directory>child</project.directory>
  </properties>

    from pydantic import BaseModel, computed_field

    class Rectangle(BaseModel):
        width: int
        length: int

        @computed_field
        @property
        def area(self) -> int:
            return self.width * self.length

    @app.get("/")
    def read_root() -> Rectangle:
        return Rectangle(width=3, length=4)

        include("**/*.json")
    }

    def isSnapshot = gradleModule.identity.snapshot
    inputs.files(acceptedViolationsFiles)
    inputs.property("baseline.version", compatibilityBaselineVersion)
    inputs.property("currentVersion", baseVersion)
    def apiSourceFolders = configurations.currentSources.incoming.artifactView { lenient(true) }.files
    inputs.files("apiSourceFolders", apiSourceFolders)

 * similar to the way Maven configures plugins from the POM, i.e. some configuration like {@code <param>value</param>}
 * is mapped to an equally named property of the bean and converted. The properties of the bean are supposed to either
 * have a public setter or be backed by an equally named field (of any visibility).
 *
 * @since 3.0
 */
public interface BeanConfigurator {

 defined the maven.multiproject.includes property in any of his properties
 files for the current project. if yes. then I'm able to find projects that
 can be offered to be opened together with the current project.
 problems with the current solution are:
 1. information is duplicate. once in POM's dependencies and once in the
 maven.multiproject.includes property.

    /*
       - The below two ignored files are generated during test execution
       by the test: okhttp/src/test/java/okhttp3/osgi/OsgiTest.java

       - The compressed index.xml file contains a timestamp property which
       changes with every test execution, such that running the test
       actually changes the test classpath itself. This means that it
       can"t benefit from incremental build acceleration, because on every

   * changes).
   */
  @Override
  public ImmutableMap<Object, Collection<Object>> asMap() {
    return super.asMap();
  }

  private Object readResolve() {
    return INSTANCE; // preserve singleton property
  }

  @GwtIncompatible @J2ktIncompatible private static final long serialVersionUID = 0;

      <groupId>test</groupId>
      <artifactId>a</artifactId>
      <version>0.2</version>
    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>b</artifactId>
      <version>${missing.property}</version>
    </dependency>
    <dependency>
      <groupId>test</groupId>
      <artifactId>c</artifactId>
      <version>1/1</version>
    </dependency>
  </dependencies>

import gradlebuild.configureAsRuntimeJarClasspath

plugins {
    java
}

interface LaunchableJar {
    /**
     * The main class for the application. Can be undefined.
     */
    val mainClassName: Property<String>
}

val app = extensions.create<LaunchableJar>("app")

val manifestClasspath = configurations.dependencyScope("manifestClasspath")

        <artifactId>good</artifactId>
        <version>1.0</version>
      </plugin>
      <plugin>
        <groupId>test</groupId>
        <artifactId>mip</artifactId>
        <version>${missing.property}</version>
      </plugin>
      <plugin>
        <groupId>test</groupId>
        <artifactId>rmv</artifactId>
        <version>RELEASE</version>
      </plugin>
      <plugin>
        <groupId>test</groupId>