hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6305) Unify build property names to facilitate cross-projects modifications
Date Fri, 09 Oct 2009 20:35:31 GMT

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

Tsz Wo (Nicholas), SZE updated HADOOP-6305:
-------------------------------------------

    Hadoop Flags: [Reviewed]

> While it certainly seems inappropriate it ought to be addressed by a separate JIRA such
your HADOOP-6159. Does it make sense?

Sure.

+1 patch looks good.  Could you also try various ant targets, especially "ant tar", to make
sure everything still working?

PS: Not sure if this is qualified to be committed to 0.21.

> Unify build property names to facilitate cross-projects modifications
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-6305
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6305
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6305.patch
>
>
> Current build files of {{common}}, {{mapreduce}}, {{hdfs}} have their own unique ways
of naming properties which otherwise have very same meaning. I.e. the locations of java source
code are called {{core.src.dir}}, {{mapred.src.dir}}, and {{hdfs.src.dir}} respectively.
> It makes modifications needed for all three projects to be very unique thus increasing
the number of difference between builds of the projects.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message