Using 'mvn -U' seems to have resolved the issue for Michael. Probably blowing away ~/.m2 would have as well.
On Wed, Sep 5, 2018 at 1:33 PM Philip Zeyliger <[email protected]> wrote: > > org.apache.hbase:hbase-procedure:jar:2.0.0-cdh6.x-SNAPSHOT > > What command are you trying to build with? > > If I had to guess, you're re-building "fe" but haven't rebuilt > "impala-parent". But it could also be something else, of course. One thing > you could do is blow away ~/.m2/repository/org/apache, or run with "mvn > -U", or run a clean build, and so on. > > If you'd like to, I'm happy to screen share with you and we can pinpoint > the problem. > > -- Philip > > On Wed, Sep 5, 2018 at 1:30 PM Michael Ho <[email protected]> wrote: > >> Thanks Philip. I am seeing this on my own machine so far. Also started a >> private build on some AWS instances to see if it's specific to my >> environment. The following is the presumably interesting part of maven >> output. Not sure if my toolchain bootstrapping screwed up or something and >> I removed toolchain/cdh-components* before retrying. It's complaining >> about >> hbase if I understand the output correctly: >> >> [DEBUG] Adding failure due to exception >> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned >> Dependency: org.apache.hbase:hbase-procedure:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-zookeeper:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-replication:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-mapreduce:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-server:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-hadoop2-compat:jar:tests:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-http:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-common:jar:tests:2.0.0-cdh6.x-SNAPSHOT >> Use 'mvn dependency:tree' to locate the source of the banned dependencies. >> at >> >> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute(AbstractBanDependencies.java:107) >> at >> >> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202) >> at >> >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:498) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) >> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies >> failed with message: >> Found Banned Dependency: >> org.apache.hbase:hbase-procedure:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-zookeeper:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-replication:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-mapreduce:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-server:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-hadoop2-compat:jar:tests:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-http:jar:2.0.0-cdh6.x-SNAPSHOT >> Found Banned Dependency: >> org.apache.hbase:hbase-common:jar:tests:2.0.0-cdh6.x-SNAPSHOT >> Use 'mvn dependency:tree' to locate the source of the banned dependencies. >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 4.335s >> [INFO] Finished at: Wed Sep 05 13:26:27 PDT 2018 >> [INFO] Final Memory: 35M/859M >> [INFO] >> ------------------------------------------------------------------------ >> >> On Wed, Sep 5, 2018 at 1:21 PM Philip Zeyliger <[email protected]> >> wrote: >> >> > Are you seeing this on your own machine? If so, try to add "-X" to the >> mvn >> > execution and capture the (very large) log. I'd be happy to take a look. >> > >> > -- Philip >> > >> > On Wed, Sep 5, 2018 at 12:34 PM Michael Ho <[email protected]> wrote: >> > >> > > 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 >> > > >> > >> >> >> -- >> Thanks, >> Michael >> >
