hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12257) rework build tool support; add gradle
Date Mon, 24 Aug 2015 20:53:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710039#comment-14710039

Allen Wittenauer commented on HADOOP-12257:

bq. part of init is detecting the branch and changing, right?

Yup. It's all the setup work that happens prior to anything actually changing on the repo.

bq.  calling "branch" something like "validate" will help folks coming from maven. I'm curious
if it would hinder ant/gradle/autoconf/whatever.

While we're using the term 'branch' today even in the existing code, it doesn't have to stay
that way.  But anyway, it's called branch to reflect the state of the repo:  "this is the
copy of source from the branch".  Log files are written such that they are xyz-testname.log,
where xyz is either branch or patch.  Then tests can compare branch vs. patch and do whatever.

bq. Do you have notes already about how the proposed lifecycle matches up on the non-java
build tools?

Not yet.  Let me write up something regarding the current state of my dev tree and it might
make more sense. :)

> rework build tool support; add gradle
> -------------------------------------
>                 Key: HADOOP-12257
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12257
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: yetus
>    Affects Versions: HADOOP-12111
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-12257.HADOOP-12111.00.patch
> We need to rework build tool support to be pluggable as well as add gradle support so
that we cover more of the ecosystem.

This message was sent by Atlassian JIRA

View raw message