lkishalmi commented on PR #5053: URL: https://github.com/apache/netbeans/pull/5053#issuecomment-1339659119
@sdedic I share your feelings. I took the plugin based ProjectService registration from Maven, where it was based on the packaging type. The multi-project Gradle projects were just started to take off and usually even with that the root project had the java plugin applied on most projects I've seen. If you have ideas, let's start a discussion. I'm open to change. Though now with the new native interfaces in Java, I'd expect more mixed languages project, where one sub-project is a C library, then the next one is a Java. You could expect a JavaExec task show up anywhere in debug mode, or get some stacktrace here and there. I could imagine, that most of these services would be registered globally. Though the output processors could be dynamic, as we can get some info from the task being executed... Regarding this JavaPlatformProviderImpl. It shall be in the Gradle Project Support. Also this setting shall be taken from the root project. That's a medium change for NB17. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- 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
