Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16311
This looks reasonable to me as a solution. I am not sure if there was a
reason the tags needed to be in one module (like to enable some certain usage
of it in the SBT build or something). I suppose the nice thing about having
them in one place is that, being just tags, this whole module can be dropped at
runtime if desired. Hence pushing the whole thing to `provided` scope is always
probably possible.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
