stack created HBASE-19725:
-----------------------------

             Summary: Build fails, unable to read 
hbase/checkstyle-suppressions.xml "invalid distance too far back"
                 Key: HBASE-19725
                 URL: https://issues.apache.org/jira/browse/HBASE-19725
             Project: HBase
          Issue Type: Sub-task
            Reporter: stack
            Assignee: stack
            Priority: Blocker


Build is failing on me (Trying to cut beta-1 RC on branch-2). It is first time 
we go to use the jars made by hbase-checkstyle in the hbase-error-prone module 
under 'build support' module when running the 'site' target. It is trying to 
make the checkstyle report.

I see that we find the right jar to read:

[DEBUG] The resource 'hbase/checkstyle-suppressions.xml' was found as 
jar:file:/home/stack/rc/hbase-2.0.0-beta-1.20180107T061305Z/repository/org/apache/hbase/hbase-checkstyle/2.0.0-beta-1/hbase-checkstyle-2.0.0-beta-1.jar!/hbase/checkstyle-suppressions.xml.

But then it thinks the jar corrupt 'ZipException: invalid distance too far 
back'.

Here is mvn output:

12667058 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on 
project hbase-error-prone: Failed during checkstyle executi         on: Unable 
to process suppressions file location: hbase/checkstyle-suppressions.xml: 
Cannot create file-based resource:invalid distance too far back -> [Help 1]
12667059 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check 
(checkstyle) on project hba         se-error-prone: Failed during checkstyle 
execution

I'm running this command:

mvn -X install -DskipTests site assembly:single -Papache-release -Prelease 
-Dmaven.repo.local=//home/stack/rc/hbase-2.0.0-beta-1.20180107T061305Z/repository


Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T08:41:47-08:00) 
Java version: 1.8.0_151, vendor: Oracle Corporation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to