Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5471#issuecomment-92027893
Yes, in general there's no special reason the children can't be built
independently ... except of course that all of their dependencies must exist!
and if they depend on SNAPSHOTs of other project modules, which aren't
otherwise published, then you have to have `install`-ed them locally first.
I can see this being a legit use case if you were, say, iterating on a test
/ patch in a child module and just wanted to keep rebuilding it. You can do it
from the top level with `-pl project`, but some expect to also be able to run
from the module itself. At least, this was prompted by a tweet declaring
Spark's Maven build so silly because this wasn't possible :)
Since this instance was fixable and appeared to be the only barrier to
building (most) child modules, and I saw some other things to update, I figured
I'd go for it. Individually none of these changes are that important. I may
have to back out the file move here if SBT can't be updated to see 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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
