On Tue, 14 Mar 2023 at 17:31, Antonio <anto...@vieiro.net.invalid> wrote: > This is very much the same we do with other external tools we may use, > such as "maven", or "npm" or "gradle" (we use our embedded "ant" though, > AFAIK).
Maven is embedded too. > The question is, shall the IDE ask the user for permission before using > any of these external commands? Or is it ok to find them in the PATH, > for instance, and start using them directly? What are the actions that will invoke the commands? Are they all actions where the user should expect code execution? If yes, I'm not sure permission is required, although might still be worth considering? If not, then sounds like a similar trust mechanism to Gradle might be needed? The Gradle trust mechanism came about mainly because it should be possible to open and inspect a project in the IDE without code execution, whereas building it you should expect. Similarly the Micronaut wizard warnings (because mvnw support was not added with background execution in mind) - https://github.com/apache/netbeans/pull/3506 Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
