assertEquals(2, cmdList.size());
        assertTrue(cmdList.contains("-Dapp.module.feature1=enabled"));
        assertTrue(cmdList.contains("-Dapp.module.feature2=disabled"));

        // Clean up
        System.clearProperty("app.module.feature1");
        System.clearProperty("app.module.feature2");
        System.clearProperty("app.service.api");
        System.clearProperty("config.app.module");
    }

### Properties of stable features

Properties of stable features MUST start with `org.gradle.<feature-name>.`

The qualifier is absent for these properties, making the name more concise.
This is a sensible default, as the majority of features are of this nature.

These properties MUST be stable.

- `@Secured` annotation with role array (`"admin-user"`, `"admin-user-view"`)
- Role-based query filtering via `RoleQueryHelper`
- Authentication: Local (UserService), LDAP, OIDC, SAML, SPNEGO, Entra ID
- Security features: AES encryption, SHA256 digest, LDAP injection prevention, password policy, rate limiting

## Naming Conventions

| Element | Convention | Example |
|---------|------------|---------|

        return this;
    }

    /**
     * Gets the list of active features.
     *
     * @return A list of active features.
     */
    public List<String> activeFeatures() {
        return activeFeatures;
    }

    /**
     * Sets the list of active features.
     *
     * @param activeFeatures A list of active features.
     * @return This query builder.
     */

## Before you start

Before starting to work on a feature or a bug fix, please open an issue to discuss the use case or bug with us, or post a comment in the relevant issue. 
This can save everyone a lot of time and frustration.

For any non-trivial change, we need to be able to answer these questions:

* Why is this change done? What's the use case?
* For user-facing features, what will the API look like?

        }

        features {
            // https://www.jetbrains.com/help/teamcity/shared-resources.html#Viewing+Shared+Resources+Usage
            // https://blog.jetbrains.com/teamcity/2013/05/explaining-the-shared-resources-plugin/
            // we only allow 1 promotion job running at the same time to avoid website xml conflicts
            feature {
                type = "JetBrains.SharedResources"

Each platform provides support for some kind of automation, such as building JVM software or building Gradle plugins.
Platforms typically extend the features of other platforms to add this support.

By understanding the Gradle platforms and their relationships, you can get a feel for where in the Gradle source tree a particular feature is implemented.

See [Gradle platform architecture](platforms.md) for a list of the platforms and more details.

### Gradle runtimes

**Web Crawling**:
- **Admin Path**: Crawler > Web
- **Supports**: HTTP/HTTPS websites
- **Features**: JavaScript rendering, authentication, custom headers

**File Crawling**:
- **Admin Path**: Crawler > File
- **Supports**: SMB, FTP, local file systems
- **Features**: Access control, file type filtering

**Data Store Crawling**:
- **Admin Path**: Crawler > Data Store

        DocumentBuilderFactory.newInstance().apply {
            setFeature("http://apache.org/xml/features/disallow-doctype-decl", true)
            setFeature("http://xml.org/sax/features/external-general-entities", false)
            setFeature("http://xml.org/sax/features/external-parameter-entities", false)
            setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false)
            isExpandEntityReferences = false

    }
}

fun BaseGradleBuildType.tcParallelTests(numberOfBatches: Int) {
    if (numberOfBatches > 1) {
        params {
            param("env.TEAMCITY_PARALLEL_TESTS_ENABLED", "1")
        }
        features {
            parallelTests {
                this.numberOfBatches = numberOfBatches
            }
        }
    }
}

fun BuildFeatures.publishBuildStatusToGithub() {