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

Peter Somogyi commented on HBASE-21443:
---------------------------------------

[~stack], my idea why yetus run scaladoc for the first patch is because it 
noticed that there were .scala files changed in the patch. It ran the scaladoc 
target for branch (original version) and it executed the same verifications on 
the patched version.

[https://github.com/apache/yetus/blob/master/precommit/test-patch.d/maven.sh#L482-L485]
 
[Tue Nov  6 21:42:47 UTC 2018 INFO]: Personality: branch scaladoc
...
[Tue Nov  6 22:16:33 UTC 2018 INFO]: Personality: patch scaladoc
 If my assumption is correct we have to allow this patch in with the yetus -1 
for scaladoc.

[~busbey]: Are there any workarounds for this?

> [hbase-connectors] Purge hbase-* modules from core now they've been moved to 
> hbase-connectors
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21443
>                 URL: https://issues.apache.org/jira/browse/HBASE-21443
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hbase-connectors, spark
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-21443.master.001.patch, 
> HBASE-21443.master.002.patch, HBASE-21443.master.002.patch
>
>
> The parent copied the spark modules over to hbase-connectors. Here we purge 
> them from hbase core repo.



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

Reply via email to