[ 
https://issues.apache.org/jira/browse/HBASE-20749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560228#comment-16560228
 ] 

Mike Drob commented on HBASE-20749:
-----------------------------------

[~busbey] - from 
https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20749/5//artifact/output-general/maven-patch-checkstyle-root.txt

{noformat}
[WARNING] The requested profile "test-patch" could not be activated because it 
does not exist.
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:checkstyle (default-cli) 
on project hbase: Execution default-cli of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:checkstyle failed: 
Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0 or one of its 
dependencies could not be resolved: Could not find artifact 
com.puppycrawl.tools:checkstyle:jar:8.12 in Nexus 
(http://repository.apache.org/snapshots) -> [Help 1]
{noformat}

This probably affects other nightly build stuff too?

> Upgrade our use of checkstyle to 8.6+
> -------------------------------------
>
>                 Key: HBASE-20749
>                 URL: https://issues.apache.org/jira/browse/HBASE-20749
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, community
>            Reporter: Sean Busbey
>            Assignee: Mike Drob
>            Priority: Minor
>         Attachments: HBASE-20749.master.001.patch
>
>
> We should upgrade our checkstyle version to 8.6 or later so we can use the 
> "match violation message to this regex" feature for suppression. That will 
> allow us to make sure we don't regress on HTrace v3 vs v4 APIs (came up in 
> HBASE-20332).
> We're currently blocked on upgrading to 8.3+ by [checkstyle 
> #5279|https://github.com/checkstyle/checkstyle/issues/5279], a regression 
> that flags our use of both the "separate import groups" and "put static 
> imports over here" configs as an error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to