Indeed Gradle keeps different types of files like sources and resources
in different subdirectories.
*.form files are another type of files, which are created and needed
even before compilation and are not to be deployed, so they would reside
in their own subdirectory aside sources and resources.
Gradle would need to be configured so that NB will find them despite
being in a different dir (don't know if that is possible), and to
exclude them from deployment…
In doubt *.form files could be deleted from the build dir after
compilation and before deployment, e.g. using doFirst in the deployment
task, something like this:
https://docs.gradle.org/current/userguide/common_caching_problems.html#custom_actions
(never tried that myself…)
Bernd
On 18.10.22 18:57, Neil C Smith wrote:
On Tue, 18 Oct 2022 at 17:51, Thorsten Schöning <tschoen...@am-soft.de> wrote:
Mostly that non-Java is exactly what is meant to be maintained in
"resources". There's not that much difference between images or XML
form files. This might even allow to not publish those files as part
of the deployment, configure different set of rules in IDEs etc.
There's a massive difference between images and .form files - .form
files are not meant to be published as part of the deployment.
Also, as far as NetBeans is concerned, they are one file - pros and
cons to that.
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
