srowen commented on PR #40933: URL: https://github.com/apache/spark/pull/40933#issuecomment-1536441189
They do transitively depend on Jackson, if it's compile scope. Lots of stuff would never work otherwise. runtime scope does not work; we could not compile against Jackson code then, and Spark uses Jackson classes. You are correct that there is a conflict that Maven resolves, and its rules may not give the desired effect. However Spark does "all it can do" by directly depending on Jackson. The only thing I can think of is to also exclude the jackson dep from Avro explicitly in the Spark POM? -- 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]
