"area": {
                                "type": "integer",
                                "title": "Area",
                                "readOnly": True,
                            },
                        },
                        "type": "object",
                        "required": ["width", "length", "area"],
                        "title": "Rectangle",

        },
        "notable": {
          "type": "boolean"
        }
      },
      "required": [
        "area",
        "title",
        "details",
        "impact"
      ],
      "additionalProperties": false
    },
    "Deprecation": {
      "properties": {
        "area": {
          "$ref": "#/definitions/breakingArea"
        },
        "title": {
          "type": "string",

    }

    public static class Breaking {
        private String area;
        private String title;
        private String details;
        private String impact;
        private boolean notable;

        public String getArea() {
            return area;
        }

        public void setArea(String area) {
            this.area = area;
        }

        public String getTitle() {

    breakingChangesByArea.eachWithIndex { area, breakingChanges, i ->
        print "\n"

        if (isNotable) {
            print "// tag::notable-breaking-changes[]\n"
        }

        print "[discrete]\n"
        print "[[breaking_${majorMinor}_${ area.toLowerCase().replaceAll("[^a-z0-9]+", "_") }]]\n"
        print "==== ${area}\n"

        for (breaking in breakingChanges) { %>

                        TreeMap::new,
                        // Group changelogs for each type by their team area
                        groupingBy(
                            // `security` and `known-issue` areas don't need to supply an area
                            entry -> entry.getType().equals("known-issue") || entry.getType().equals("security")
                                ? "_all_"

  - release-team-subproject-leads
  - satyampsoni # 1.32 Release Notes Lead
reviewers:
  - release-managers
  - release-team-subproject-leads
  - satyampsoni # 1.32 Release Notes Lead
labels:
  - sig/release

	</component>

	<component name="allChildUrlRuleMap" class="java.util.LinkedHashMap">
		<postConstruct name="put">
			<arg>"//A"</arg>
			<arg>"href"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//AREA"</arg>
			<arg>"href"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//FRAME"</arg>
			<arg>"src"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//IFRAME"</arg>

                    );
                }

                if (entry.getArea() == null) {
                    throw new GradleException(
                        "[" + path + "] must provide an [area] (only 'known-issue' and " + "'security' entries can omit this"
                    );
                }
            }

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".

//
//   - Optional: Set server preferences for Backup & Replication parallel sessions, batch size of deletes, and block sizes (before
//     compression). This is an optional area; by default, there should be no <SystemRecommendations> section in the
//     system.xml. Vendors can work with Veeam Product Management and the Alliances team on getting approval to integrate