[
https://issues.apache.org/jira/browse/HBASE-21443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678269#comment-16678269
]
Sean Busbey commented on HBASE-21443:
-------------------------------------
Peter has it exactly correct. It's just that Yetus sees scala files have
changed and the scaladoc test is around (because we tell it to use "all" tests
basically) so it tries to run the test on the presumption that a maven project
with scala files will have configured the scala plugins.
Yetus would be more robust here if it referred to the fully qualified maven
plugin name. we should file a bug for that.
In general I think the workaround is to treat this as a false error and ignore
it.
> [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)
