"required": ["price"],
                    "type": "object",
                    "properties": {"price": {"title": "Price", "type": "integer"}},
                },
                "Item": {
                    "title": "Item",
                    "type": "object",
                    "properties": {
                        "name": {
                            "title": "Name",

        Properties userProperties = new Properties();
        Map<String, String> paths = context.extraInterpolationSource();

        // ----------------------------------------------------------------------
        // Options that are set on the command line become system properties
        // and therefore are set in the session properties. System properties
        // are most dominant.

        }
    }

    private
    fun readTestClasses(content: String): Map<String, List<String>> {
        val properties = Properties()
        val ret = mutableMapOf<String, MutableList<String>>()
        properties.load(StringReader(content))
        properties.forEach { key, value ->
            val list = ret.getOrDefault(value, mutableListOf())
            list.add(key!!.toString())

    }

    private
    fun createProperties() = Properties().also { properties ->
        properties["runtime"] = runtime.get().joinToString(",")
        properties["projects"] = projects.get().joinToString(",")
        optionalProjects.get().takeIf { it.isNotEmpty() }?.let { optional ->
            properties["optional"] = optional.joinForProperties()
        }
    }

    private

## Decision

### Types of properties that should not use lazy types

The guidelines below do not apply to all properties. There are cases where the lazy types should not be used:

#### Non-calculated values

These are inappropriate uses of lazy types:

```groovy
class Example {

    return new ValueGraphBuilder<>(false);
  }

  /**
   * Returns a {@link ValueGraphBuilder} initialized with all properties queryable from {@code
   * graph}.
   *
   * <p>The "queryable" properties are those that are exposed through the {@link ValueGraph}
   * interface, such as {@link ValueGraph#isDirected()}. Other properties, such as {@link
   * #expectedNodeCount(int)}, are not set in the new builder.
   */

                    "type": "object",
                    "properties": {"data": {"$ref": "#/components/schemas/Product"}},
                },
                "Body_create_shop_shops_post": {
                    "title": "Body_create_shop_shops_post",
                    "required": ["data"],
                    "type": "object",
                    "properties": {
                        "data": {"$ref": "#/components/schemas/Shop"},

      </activation>
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
      </properties>
    </profile>
    <profile>
      <id>file</id>
      <activation>
        <file>
          <exists>simple.xml</exists>
        </file>
      </activation>
      <properties>
        <profile.file>activated</profile.file>
      </properties>
    </profile>
  </profiles>

                    "type": "object",
                    "properties": {"message": {"title": "Message", "type": "string"}},
                },
                "ValidationError": {
                    "title": "ValidationError",
                    "required": ["loc", "msg", "type"],
                    "type": "object",
                    "properties": {
                        "loc": {

        resource.addInclude("*.xml");
        resource.addInclude("*.properties");

        // Verify both includes are present
        assertEquals(2, resource.getIncludes().size(), "Should have two includes");
        assertTrue(resource.getIncludes().contains("*.xml"), "Should contain *.xml");
        assertTrue(resource.getIncludes().contains("*.properties"), "Should contain *.properties");

        // Verify persistence