sdedic commented on PR #4517: URL: https://github.com/apache/netbeans/pull/4517#issuecomment-1234236277
Let's focus back on the topic of gathering information. To build `native-image` support, I'd need some information from the extension / task that is configured for the project. I agree that instantiating tasks (= user code) could be dangerous. It seems that instantiation happens every time, just because we're **enumerating tasks** from the buildscript, so we can (for example) present them, for example, in the `Navigator` window for a gradle project. Not only Jar task, which will be eventually executed as the part of buildscript, but all of them - e.g. `OutgoingVariantsReportTask` (`./gradlew oV`) is instantiated. So, if the concern that task creation is harmful is valid and important, we should remove the task listing code and corresponding feature(s) in the IDE (or implement them using another technique). Given that this feature is in the Gradle Projects module for some years already, with no significant bug reports against ... I would not go that way: it might be bad (this is why we have 'Do you trust the build script' question, among other reasons) ... but seems acceptable. If there Tasks already instantiate ... why don't exploit the data then, so the IDE can evaluate using the most accurate values ? -- 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
