Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/11803#issuecomment-198314377
As you explained in #8598, I understand the need to have Maven 3.3.x
version (instead of Maven 3.2.x). It makes complete sense. The point in this PR
is the fact that we "force" the latest Maven 3.3.x version, whereas the build
works fine with another version in the Maven 3.3.x serie.
@srowen it's weird as build/mvn doesn't download the latest version of
Maven on my box, it uses the one installed:
spark$ ./build/mvn -DskipTests clean package
Using `mvn` from path: /opt/apache-maven-3.3.3/bin/mvn
...
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
Detected Maven Version: 3.3.3 is not in the allowed range 3.3.9.
I think using enforcer [3.3,) rule for Maven version would be more
"flexible".
Let me know what it makes sense, else I will close this PR.
Thanks !
---
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]
