Task Execution
As with the Maven plugin, if you don't want to run unit tests just because executing the build command, you should check this. Technically, this will add "-x test" as an argument to appropriate commands.
If you don't want to run the check task just because executing the build command, you should check this. Technically, this will add "-x check" as an argument to appropriate commands.
If this is not checked, the plugin will append to the output window of non-blocking tasks (non-blocking tasks are tasks marked so, that is, you wish to wait for them to terminate before starting other tasks). If checked, the output window will be cleared after starting a new Gradle task. Choose your preference.
When you type something in the output window, Unix line separators ('\n' characters) will be replaced with the platform specific line separator. The reason to have this enabled is that Gradle won't forward the input to the build script's standard input until it receives the platform specific line separator.
By default the plugin will add an init script to execute before your tasks. This should not interfere with your build as it only adds "run" and "debug" tasks if you did not add them manually. Regardless, it is technically possible to write a build script which fails with the init script added, so you have the option to disable automatically adding this init script. These are the currently supported options:
- NetBeans should add tasks automatically (e.g.: run): This is the default value. The appropriate build scripts will be applied to your projects before task execution. If you don't experience any problem, you should use this setting because the init scripts are required for some feature to work properly.
- NetBeans should not add tasks automatically: NetBeans will not apply any additional init script (except those specified by you) to your build. Selecting this setting might cause some features to not work as before (e.g.: running and debugging)
- Manually maintain NetBeans' init script: If you select this setting, on the first task execution attempt (even unsucessful ones) the init scripts applied will be created in ~/.gradle (unless they are already there) and will be used from there on instead of the init script packaged into this plugin. If you remove the applied init scripts, they will be recreated when needed again. These file can be found under the Build Scripts/Gradle Home node. Warning: If you select this setting, next time the plugin will be updated, the changes in the init script will not be available to you (unless you manually remove your init scripts). Use this setting only if you really need it.