Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to define default convention for specific Property types #14363

Open
ljacomet opened this issue Sep 1, 2020 · 2 comments
Open

Ability to define default convention for specific Property types #14363

ljacomet opened this issue Sep 1, 2020 · 2 comments
Labels
a:feature A new functionality in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty

Comments

@ljacomet
Copy link
Member

ljacomet commented Sep 1, 2020

While working on Java toolchains, we encountered a scenario where having a default convention on a created property would make sense:
In the context of a java project, it would be great if any task that uses a JavaLauncher (the toolchain provided java reference) would see its instance with the java extension toolchain convention.
Right now the wiring happens per plugin / per task.

If one could register default convention mappings on the property factory, the above could be simplified and also implicit for plugin authors leveraging toolchains in Gradle.

@ljacomet ljacomet added in:core DO NOT USE a:feature A new functionality labels Sep 1, 2020
@ljacomet
Copy link
Member Author

ljacomet commented Sep 1, 2020

@adammurdoch As discussed today

@ljacomet ljacomet added in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty and removed in:core DO NOT USE labels Jun 28, 2021
@bric3
Copy link
Contributor

bric3 commented Sep 29, 2021

Any news on this one ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:feature A new functionality in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty
Projects
None yet
Development

No branches or pull requests

3 participants