You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/07/07 22:55:05 UTC

[jira] [Updated] (HADOOP-12198) patches that hit multiple modules may need to build at root

     [ https://issues.apache.org/jira/browse/HADOOP-12198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated HADOOP-12198:
--------------------------------------
    Attachment: HADOOP-12198.HADOOP-12111.00.patch

After many failed attempts, this is what I've come up with:

00:
* add a CHANGED_UNION_MODULES var which determines a common module based upon all the changed ones
* change javac from compile to test-compile to make sure that maven plugins get their descriptor built
* change the hadoop personality to always javac . if hadoop-common changes, use union if not
* add the directory to the maven output log to help debugging
* the find_*_dirs no longer exit on failure and instead callers should check for empty or the return code
* 

> patches that hit multiple modules may need to build at root
> -----------------------------------------------------------
>
>                 Key: HADOOP-12198
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12198
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: yetus
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-12198.HADOOP-12111.00.patch
>
>
> Patches that introduce dependencies on other modules (e.g., HADOOP-12180) need to effectively built at root. 
> There is a good chance this type of logic will need to be done on a per-project basis. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)