neilcsmith-net commented on issue #8648: URL: https://github.com/apache/netbeans/issues/8648#issuecomment-3077822440
There are a few other things there, in particular working with the dependency graph, and building the relevant classpaths, etc. I guess that _might_ still be achievable using Maven output. In particular if we used the embedded mode of `ExecutorTool` for some things. I think it comes down to which is the easier approach / least work. There are also MIMA and [Toolbox](https://maveniverse.eu/docs/toolbox/plugin-documentation/plugin-info.html) directly that might be worth looking at. Again comes to looking at how much work is required to modify what we have vs adapt to something else. I don't know where LSP fits in unless there's an existing third-party project you have in mind? I don't see `mvnw` as adding clutter - it's about locking required build versions. Having a version of `mvn` you don't need is also clutter. The key thing for me is that if we started with using `mvnw` in new projects, recommending if missing, etc. we could consider upgrading the parsing stuff before Maven 4 final is released. We had a similar thing in the past with RCs of Gradle tooling - if used internally we need to ensure that doesn't "leak" into users' projects. -- 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
