[
https://issues.apache.org/jira/browse/HADOOP-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710003#comment-14710003
]
Sean Busbey commented on HADOOP-12257:
--------------------------------------
I think it will help folks grok the lifecycle if we have rough mapping to
extant lifecycles (it'll also help make clear why all of the existing build
tool lifecycles are insufficient--I presume due to the fact that we have
mirrored phases pre/post patch).
Initial thoughts:
* part of init is detecting the branch and changing, right?
* calling "branch" something like "validate" will help [folks coming from
maven|https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference].
I'm curious if it would hinder ant/gradle/autoconf/whatever.
Do you have notes already about how the proposed lifecycle matches up on the
non-java build tools?
> 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
(v6.3.4#6332)
