Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17416
Well it's a little different, now that I've modified the tests to cover the
classifier case. In this case, when the main artifact has a classifier, it
doesn't find the dependency that the test sets up. It's definitely declared
correctly in the POM that's created. I'm guessing somehow adding the
DependencyArtifactDescriptor prevents it from attempting resolution or
something. Still looking into it...
---
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
