Use configuration names in `AbstractDependencyReportTask` about gradle HOT 4 OPEN

Hi there,

I'm looking around for places I can jump in and contribute. Wanted to clarify a few points about this issue:

1. Is the primary goal to create helper get() methods for each member in the Configuration set? I see you mentioned "using bytecode upgrades to make the change seamless." I'll do some reading on this to learn more about how to implement as similar approach.
2. I also see a getConfigurationsWithDependencies() method just below the referenced getConfigurations() method. Is this second method also in scope for this issue?

Thank in advance for your time!

from gradle.

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

Should we change the type here or add a String based SetProperty instead?

@major-mira666 This is probably not the best issue to start on. Take a look at good first issue or help wanted labels.

from gradle.

Thanks! Appreciate the prompt response. Just started my work week back up, so I will prowl each of those labels next weekend.

Have a great week!

from gradle.

Discussion: there is value in migrating this to the provider API, but the main usage of the property is form the command-line, so the main benefit of migration would be consistency only. We can de-prioritize this and migrate only as a nice-to-have.

from gradle.