Hi all,
I tried a clean build this morning and kept running into the following
errors when building the FE code:
[WARNING] Could not transfer metadata
com.cloudera.cdh:cdh-root:6.x-SNAPSHOT/maven-metadata.xml from/to
${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}): No connector available to
access repository ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}) of type
default using the available factories WagonRepositoryConnectorFactory
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
failed with message:
[INFO] BUILD FAILURE
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
(enforce-banned-dependencies) on project impala-frontend: Some Enforcer
rules have failed. Look above for specific messages explaining why the rule
failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
mvn -B install -DskipTests exited with code 0
make[3]: *** [fe/CMakeFiles/fe] Error 1
make[2]: *** [fe/CMakeFiles/fe.dir/all] Error 2
make[1]: *** [fe/CMakeFiles/fe.dir/rule] Error 2
make: *** [fe] Error 2
I believe Bharath filed https://issues.apache.org/jira/browse/IMPALA-7526
for this. Philip mentioned in past code review that log4j2 is the offender.
Did anyone else run into it ?
--
Thanks,
Michael
