[ https://issues.apache.org/jira/browse/HBASE-19690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315363#comment-16315363 ]
stack commented on HBASE-19690: ------------------------------- Why verify? Why aggregate javadoc when pom does that? Then why skip javadoc? Where did this assortment of a command come from? It worked from scratch or was it a continuation? It works for default profile? I can try but this unorthodox and it takes time building and perhaps you have answers? > Maven assembly goal fails in master branch with 'invalid distance too far > back' > ------------------------------------------------------------------------------- > > Key: HBASE-19690 > URL: https://issues.apache.org/jira/browse/HBASE-19690 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > > I use the following command in master branch : > {code} > mvn clean verify install javadoc:aggregate package assembly:single > -DskipTests=true -Dmaven.javadoc.skip=true -Dhadoop.profile=3.0 > {code} > It fails with the following error: > {code} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on > project hbase-error-prone: Failed during checkstyle execution: Unable to > process suppressions file location: hbase/checkstyle-suppressions.xml: Cannot > create file-based resource:invalid distance too far back -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)