After learning Gradle through Android environments, there is but no option to migrate from Ant to Gradle, also for revision of historic pure-Java projects, using e.g. the Gradle plugin for Netbeans. Thus, for your consideration:
To make it swift and easy to migrate, Gradle should (must) put resources in a folder where the Java system and the programmer expects to find it, which is typically (or at least traditionally) in a /resources subfolder to where the code is.
The current solution of the Java plugin is cumbersome and easily a timethief. Why? There are two options:
Reprogram and give the getResource() method a relative path to resources found high above in the hiearchy, like …/…/… /resources, or
Instruct Gradle to put resources like this:
output.resourcesDir = “build/classes/java/main/bla/bla/bla/bla”
Not that hard, but cumbersome and you need to use time to detect this solution. In addition I could not find anything on this major migration issue in the user manual?
Do you want to make it easy for ant people to migrate? OK, then put resources next to code in a /resources subfolder. You could add a separate keyword to enable that easily for those who need it in such a migration processes, however it should really be default because Java expects what it expects.
Hope for a comment!