Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2318#issuecomment-54899349
pluginManagement by itself never activates a plugin. But crumbs I suppose
the install plugin is inherited as an active plugin from Maven's own
default POM. Aha, well, configure it in the parent, set config skip=true
there, and set it to false in children? That has worked for me elsewhere.
On Sep 8, 2014 11:47 PM, "Marcelo Vanzin" <[email protected]> wrote:
> I'm not suggesting putting it in but just configuring it in
>
> That's what I meant. If you do that, it will be executed for the
> "spark_parent" pom and will fail. (BTW that's the first thing I tried.)
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/2318#issuecomment-54898831>.
>
---
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]
