homberghp commented on issue #8648: URL: https://github.com/apache/netbeans/issues/8648#issuecomment-3074780825
> > One is to use the mvnw wrapper as execution vehicle for the time. > > We already default to using `mvnw` for the build if it's included in the project. > > My suggestion was actually that we _might_ take this opportunity not to bundle the whole of Maven, but just the libraries necessary to run the queries _inside_ the IDE. We don't bundle all of Gradle in the IDE. If by 'queries' you mean support in the editor to reflect on the Maven model (POM files) to provide hints and errors, then I wholeheartedly agree. This would simplify the NB specific code a lot. AFAIK, running `mvnw` or `mvn` does not make a big difference on the command line. It ensures that the wrapped version is the one desired by the project and avoids forcing the user to install maven. It is, of course, a bit of clutter on the users storage, but storage is cheap. Also, the user always has the option to run the (also always) included `pom.xml` file with a normal maven. The only things that NB should know about maven is: * What a valid model file looks like and how to generate hints. * Understand the feedback given by a maven exec, as in interpreting the maven output. All in all this might also suggest that an LSP solution might be appropriate. -- 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
