Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-215756534
Yeah these are separable. Really, adding the annotation requires the build
change, and the latter grew to dominate the change.
Hm, I had suggested using `<classifier>tests</classifier>` to depend on
test artifacts. I wonder if that's not the standard way to do it? it's how I've
expressed this in the past. But I also see examples of `<type>test-jar</type>`
@vanzin you probably know this better than I. However I don't know if that's
the issue here.
This particular failure is turning up from lots of tests, that are in
modules with nothing to do with the test tags. Was the last change to declare
all these 'tags' dependencies the problem? most modules have nothing to do with
it. They're just annotations... they don't matter to any logic.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
