Well, that's happening as the runSingle task has the System.in connected
in order to let some students play with the Scanner and Console.
It seems Gradle Configuration cache does not like that. That's why the
warning.
On 2/14/22 13:52, Scott Palmer wrote:
I was running a specific class from my project by right-clicking and selecting "Run
File…" and noticed this warning:
Deprecated Gradle features were used in this build, making it incompatible
with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
See
https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings
It seems to be coming from the injected ‘runSingle’ task, as I don’t get it
otherwise. Does that make sense?
Regards,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
