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 |
|---------|------------|---------|

## 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"

    }
}

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

fun BuildFeatures.publishBuildStatusToGithub() {

    "crossVersionTests": false
  },
  {
    "name": "project-features",
    "path": "platforms/core-configuration/project-features",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "project-features-api",
    "path": "platforms/core-configuration/project-features-api",
    "unitTests": false,
    "functionalTests": false,

        "platforms/documentation/docs/src/docs/release/release-notes-assets/",
        "subprojects/launcher/src/main/resources/release-features.txt",
        "platforms/core-runtime/launcher/src/main/resources/release-features.txt"
    ));

    public static void main(String[] args) throws Exception {
        if (args.length != 0) {

In addition, some of these discussions included proposals for having a single Java version supported by the Gradle Launcher and Daemon.
However, this would limit the ability of the Gradle ecosystem plugin authors to take advantage of new Java features and improvements.

One example is when one of the most popular plugins started requiring Java 17 because the underlying framework behind the plugin began requiring 17, and code from the framework was used in the plugin itself.

    /** Configuration prefix for Fess settings. */
    public static final String FESS_CONFIG_PREFIX = "fess.config.";

    /** Xerces feature prefix for XML processing. */
    public static final String XERCES_FEATURE_PREFIX = "http://apache.org/xml/features/";

    /** Load external DTD feature name. */
    public static final String LOAD_EXTERNAL_DTD_FEATURE = "nonvalidating/load-external-dtd";