sdedic commented on issue #8706: URL: https://github.com/apache/netbeans/issues/8706#issuecomment-3154751115
Well, I am not sure if it is an improvement. First, it happens for Gradle 8.5 project too (wrapper configured to use G 8.5, debugger shows the actual runtime classes from G 8.5 distribution). Then, the message is a result of `NetBeansRunSinglePlugin.configureJavaExec` calling `JavaExec.setStandardInput` - without that, the `config cache` error does not appear. I've traced this back to 7e5e8f3 by @matthiasblaesing (?). Last, I've during debugging I've tried to repeatedly run a gradle project from NB IDE (Run action on project node). But our `NetBeansRunSinglePlugin` was applied only **the first time**, subsequent runs did not apply our plugin at all - all settings were apparently loaded from the cache. I wonder if we **really** want so much caching for IDE purposes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
