internal

Move development binary convention to `NativeBasePlugin`

Decorate all domain collection container for emitting build ops (#7876)

* Update all domain object container with decorator for tracing executed callback actions

* Add decorator to a ll required occurances of DefaultDomainObjectSet

* Keep ctor for DefaultPolymorphicDomainObjectContainer as its used in gradle-idea-ext plugin

* Bring back DefaultDomainObjectSet constructor used by the android plugin

* keep backwards compatibility

Remove unused references to TargetMachineFactory

Move `TargetMachineFactory#host()` to internal API

Isolate native service and class within `platformNative` project

Move TargetMachineFactory up to a project service

Add support for declaring target machines

Wire in architecture to target machine definition

Change the C++ tooling model builder so that it does not attempt to resolve task dependencies to infer how to build the various C++ binaries, Instead add properties to the C++ project model to allow the builder to query these tasks and build logic to explicitly define what they should be.

Publish inherited exclude rules

Prior to this commit, only exclude rules directly declared on published

configurations (e.g. `apiElements` and `runtimeElements` for Java) were

published in the Ivy descriptor, POM, and Gradle metadata. Now, exclude

rules from superconfigurations (e.g. `api` for Java) are also taken into

account.

Fixes #6766.

Add `HasMultipleValue.finalizeValue()` method to allow the value of a collection property to be made final. Attempts to change the property value after this method is called will fail.

Use this in the native plugins and remove the internal `LockableCollectionProperty` implementation as it is no longer needed.

Quick fix for native dependencies that expose headers as directories

Change `ObjectFactory` so that it creates list and set properties with no initial value, rather than with an empty collection as the initial value.

Added an `empty()` method as a convenience to use when constructing these kinds of properties.

Replace all usages of the property factory methods on `ProjectLayout` and `DefaultTask` with the factory methods on `ObjectFactory`.

Expose the variant name and header directories for each C++ binary in the C++ tooling model.

Rework construction of the native binary models so that the binary names are not formatted and parsed a bunch of times during construction and so do not lose information.

Add a tooling model that provides the main C++ component and test suite of a particular Gradle project.

Moved the C++ tooling model builders into their own project separate from `language-native`.

Use immutable file collections whenever possible (#5797)

- Stop DefaultProject implementing FileOperations/ProcessOperations

- Stop BasicScript implementing FileOperations/ProcessOperations

- FileResovler.resolveUri() is not nullable

Normalize `ModuleIdentifier`

This commit reworks the `ComponentModuleIdentifier`/`ComponentModuleSelector`/`ModuleVersionSelector`

classes to use `ModuleIdentifier` under the hood, instead of storing denormalized strings. This has

the advantage that we can reduce the use of the module identifier factory, which is called very

often during dependency resolution. Sharing instances reduces the need for conversions, and makes

comparisons faster.

Interfaces for C++ model using tooling APIs

Fix the `cpp-unit-test` plugin so that it makes implementation dependencies of the main component visible to the test suite. Reworked the dependency between the test binary and the binary under test for the `cpp-unit-test` and the `xctest` plugins, so that it is implemented consistently (for later extraction into a base plugin) and is wired in via the various configurations.

Deprecate DeferredConfigurable

Remove it from the publishing plugins, as they no longer require it.

Add common base class for immutable NativePlatform

Publish configuration-wide excludes in Ivy metadata

Resolves #4356.

Add operatingSystem convenience and target builder factory methods

Rename `CapabilitiesDescriptor` to `Capabilities`

... and `getCapababilitiesMetadata()` to `getCapabilities()` for consistency.

Wire operatingSystem into Swift binary types

Publish capabilities to Ivy/Maven repositories

This commit makes sure that capabilities can be published to Maven or Ivy repositories.

By published, we only mean using Gradle metadata: capabilities are a Gradle-only feature,

so there's no equivalent to be published in a `pom.xml` or `ivy.xml` file.