I am using processResources to “filter” build information (timestamp, id, etc.) into a properties file that is then packaged into a jar or war archive and thereby made accessible to a Java-based application. This is a familiar use case and the gradle implementation works well for it.
But I would like to extend this mechanism to non-java-based builds as well. It might be useful to include such a properties file in other packages, which could somehow be read by the code in these packages, parsed, etc.
Would I have to manually invoke processResources for such cases? Or is there a more generic functionality I could use in such cases?