sdedic commented on issue #4923: URL: https://github.com/apache/netbeans/issues/4923#issuecomment-1306981881
> > Seems a strong argument in favour of a plugin or similar that runs on the target JDK and not the runtime JDK of the IDE to me! AFAIK NetBeans _can_ do a better job here, since we do not tell Gradle any JDK (so it chooses the one the tooling API within NB executes on). But - it's the user who shoudl decide. Based on my experience, both scenarios are valid: - compile on the JDK set as compile target - compile on user-chosen JDK *different* from the compilation target: the user may want to use e.g. extended syntax, especially with newer javacs that compile against exact target's JDK API set. We do not have a separate setting for the (external, forked) build tool though - and such setting might be useful even for Maven. -- 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
