build-parameters
build-parameters copied to clipboard
gradlex-org
Compile-safe access to parameters supplied to a Gradle build
Make it clear that it's not about modelling any build input coming from e.g. `gradle.properties`.
it's pretty much never safe to use any kind of secret as an argument as the command line will record it in history, build tools often preserve these in logs...
We discussed to try out spotless instead of checkstyle as a follow up to this _Originally posted by @britter in https://github.com/gradlex-org/build-parameters/pull/4#discussion_r904126933_
## Context It's common to have a set a parameters that are required in lots of projects. Examples from the GradleX organization are the CI flag as well as the...
When working with builds, sometimes we cannot control the names that variables have. For instance, when running a build from Android Studio a flag is passed called "android.injected.invoked.from.ide". It would...
If I want to modularize or have multiple generated `build-parameters` plugins that get pulled into the same build, I need to customize `PACKAGE_NAME`, `PLUGIN_CLASS_NAME`, `GENERATED_EXTENSION_NAME`, `GENERATED_EXTENSION_CLASS_NAME` to avoid namespace clashes....
See the example given in #122: Parameters are rendered in the order they are declared (?). We should sort the list alphabetically when rendering.
In the beginning we used the `./samples` build to quickly iterate on plugin features and to have an example on how to use the plugin. Later on we introduced exemplar...
Given I run some build like `./gradlew build -Pfoo=bar` it would be great to have a way to figure out whether `buildParameters.foo` was used in this build invocation. In the...
Dependatbot added support for automatically updating dependency versions declared in Gradle version catalogs. If we define dependencies and plugin versions using the catalog, we will get automatic dependency updates from...
Metadata
Owner
Metadata
Compile-safe access to parameters supplied to a Gradle build