consider changing generateJava task name

[xenoterracide]

so, I use many plugins that generate java. I just feel fortunate that none of them have also decided to use that for their task/extension name.

Maybe you could consider in a future major version providing a migration path to DgsGenerateJava and related accessors to avoid conflicts? Honestly not certain how Gradle would behave if the accessor conflicted. Accessor name probably being a bigger problem than class name which can be qualified.

[srinivasankavitha]

Thanks for the feedback, you bring up a very valid point. Unfortunately, this is not a trivial change and we would have to think about how to even manage this type of breaking change. For now, though, we will not be planning to do this in the near future due to higher priorities and hence will close this issue.