[ https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176558#comment-14176558 ]
Misty Stanley-Jones commented on HBASE-12294: --------------------------------------------- Yes, using this command: {code} mvn -e clean package javadoc:aggregate site site:stage -DskipTests {code} > Can't build the docs after the hbase-checkstyle module was added > ---------------------------------------------------------------- > > Key: HBASE-12294 > URL: https://issues.apache.org/jira/browse/HBASE-12294 > Project: HBase > Issue Type: Bug > Components: build > Reporter: Misty Stanley-Jones > Priority: Critical > Attachments: HBASE-12294.patch > > > Since the 15th, I have not been able to build the docs. I get these errors: > {code} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project > hbase-checkstyle: Missing distribution management in project HBase - > Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) -> [Help 1] > {code} > {code} > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on > project hbase-checkstyle: Missing distribution management in project HBase - > Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > 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:108) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Missing > distribution management in project HBase - Checkstyle > (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) > at > org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762) > at > org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249) > at > org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320) > at > org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281) > at > org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163) > at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > {code} > I'm able to resolve it by adding the attached patch to the POM. [~eclark], is > there a specific reason you didn't use inheritance in the checkstyles module? -- This message was sent by Atlassian JIRA (v6.3.4#6332)