hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19089) Fix the list of included moduleSets in src and binary tars
Date Fri, 27 Oct 2017 01:08:00 GMT

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

Sean Busbey commented on HBASE-19089:
-------------------------------------

{quote}
Sean Busbey Are you referring to these tests: https://builds.apache.org/job/HBase%20Nightly/?
But they are already red.
So far, i have been testing by running steps 3 and 4 of Making a release candidate and checking
the contents of tarball.
{quote}

Yes. the nightly test there includes an automated test that the source tarball can be created
and that what it makes can generate a binary.

Currently, that test is just in the Jenkinsfile, which means you need to push a branch to
try out changes. If you'd prefer to avoid doing that, file a JIRA about moving the test into
a script and I'll get it done.

> Fix the list of included moduleSets in src and binary tars
> ----------------------------------------------------------
>
>                 Key: HBASE-19089
>                 URL: https://issues.apache.org/jira/browse/HBASE-19089
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>         Attachments: HBASE-19089.master.001.patch
>
>
> List of moduleSets included in src.xml and hadoop-two-compat.xml differ quite a lot.
Particularly, hadoop-two-compat.xml is missing quite a few modules.
> The core issue is duplication involved in <included> list. Let me try to get rid
of it by using a shared list and including it using <componentDescriptor>



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

Mime
View raw message