Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2221#issuecomment-54216391
@pwendell Ah, of course. It's just that it runs "clean, test" for each
module, not "clean" for all modules, then "test" for all modules. So when a
subsequent "clean package" kicks off, it doesn't get to cleaning the assembly
until after tests like core have already failed.
So, this PR is kind of a hack, which also forcibly deletes assembly/target
right at the start in the parent's clean lifecycle. A different, perhaps better
answer is to "mvn clean && mvn ... package" in Jenkins.
WDYT?
---
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]
