Cédric Champeau
Cédric Champeau
For this you have a much simpler solution which is `tasks.names.contains(...)`. This issue is really about being able to configure a task if it happens to exist at some point...
I stumbled upon the same problem. Take this script: ``` abstract class MyTask extends DefaultTask { @Input abstract Property getWhoAmI() @Input @Optional abstract ListProperty getStrings(); @TaskAction void doSomething() { print("Task...
> That said, I would like to understand better the use cases for checking whether a property has its value explicitly assigned or via convention, as suggested by @melix, possibly...
That's correct. There's a chicken and egg problem I haven't figured out yet.
You just have to take a look at what the Maven and Gradle plugins do. They both make use of the common [reachability metadata module](https://github.com/graalvm/native-build-tools/tree/master/common/graalvm-reachability-metadata) (published on [Maven Central](https://repo1.maven.org/maven2/org/graalvm/buildtools/graalvm-reachability-metadata/0.9.27/)).
I don't know, I didn't really look at it recently. @sbglasius surely knows.
It is included in the groovy jar. What makes you think it is omitted?
@jkuipers sorry for the late answer, I'm back from a break. The explanation makes sense to me.
Thanks for your patience, I just merged it.
> As a Scala developer, I use sbt over Maven or Gradle. [off]You can use the Scala support in Gradle too[/off] > I'd like to know if you have some...