vrozov commented on PR #52725: URL: https://github.com/apache/spark/pull/52725#issuecomment-3563729447
> This seems like something that should be in the users sbt plugins if they want Yes, this is an option as well as making a local change and not committing it. Neither options are considered to be "best practice". 1. SBT: "You can create $HOME/.sbt/1.0/plugins/build.sbt and put addSbtPlugin() expressions in there to add plugins to all your projects at once. Because doing so would increase the dependency on the machine environment, this feature should be used sparingly. See [Best Practices](https://www.scala-sbt.org/1.x/docs/Best-Practices.html#global-vs-local-plugins)." 2. SBT itself adds the plugin to its own [plugins.sbt](https://github.com/sbt/sbt/blob/7b26748599e198ca461a1ee5f80712fd47255030/project/plugins.sbt#L12) It would be good to understand the downside and/or concerns of enabling sbt dependency tree plugin by default. Personally, I found it useful while investigating Kinesis and Hive where Spark SBT handles dependencies differently from 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]
