hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-9078) Downstream build including hbase-client fails because can't find com.sun.jdmk:jmxtools
Date Mon, 29 Jul 2013 23:05:49 GMT
stack created HBASE-9078:
----------------------------

             Summary: Downstream build including hbase-client fails because can't find com.sun.jdmk:jmxtools
                 Key: HBASE-9078
                 URL: https://issues.apache.org/jira/browse/HBASE-9078
             Project: HBase
          Issue Type: Sub-task
            Reporter: stack
            Assignee: stack
             Fix For: 0.95.2


I've hacked up a downstream maven project.  If I include hbase-client, my build fails with
this:

{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.821s
[INFO] Finished at: Mon Jul 29 15:58:39 PDT 2013
[INFO] Final Memory: 4M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project client: Could not resolve dependencies for project
org.hbase.downstream:client:jar:1.0-SNAPSHOT: The following artifacts could not be resolved:
com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1: Failure to find com.sun.jdmk:jmxtools:jar:1.2.1
in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will
not be reattempted until the update interval of central has elapsed or updates are forced
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project
client: Could not resolve dependencies for project org.hbase.downstream:client:jar:1.0-SNAPSHOT:
The following artifacts could not be resolved: com.sun.jdmk:jmxtools:jar:1.2.1, com.sun.jmx:jmxri:jar:1.2.1:
Failure to find com.sun.jdmk:jmxtools:jar:1.2.1 in http://repo.maven.apache.org/maven2 was
cached in the local repository, resolution will not be reattempted until the update interval
of central has elapsed or updates are forced
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
	at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
	at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
	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)
{code}

Digging, the 1.2.15 log4j pulled in by our transitive zk include has "bad metadata" -- see
http://stackoverflow.com/questions/9047949/missing-artifact-com-sun-jdmkjmxtoolsjar1-2-1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message