gwinstanley commented on issue #9157: URL: https://github.com/apache/netbeans/issues/9157#issuecomment-3789782196
Interesting, as I thought (at least historically) there was a Gradle version bundled. As I mentioned in my original post, there currently exist two options: (1) prefer wrapper, (2) custom. I'm interested in another option which chooses the wrapper if present, or a custom Gradle if not. Not all projects have a wrapper definition, so having a suitable fallback seems to make sense. Until recently I've mostly been using a custom Gradle option, pointing to a symlink for my own Gradle installation. However this doesn't accommodate some projects (e.g. web projects) which currently need an older Gradle version to work correctly with NB IDE interface. My most typical workflow is actually to _not_ use wrapper during development (then hard-define it at point of release), as I aim for most of my own projects to use cutting-edge versions where possible, and this seems the simplest workflow. However, some projects clearly need to override this and use older versions. Yes, I could indeed define wrappers for every project, yet it adds yet another layer of admin burden. This seems likely a simple enhancement to NB, although admittedly not a priority, hence a feature request rather than bug report. -- 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
