[
https://issues.apache.org/jira/browse/HADOOP-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764179#action_12764179
]
Konstantin Boudnik commented on HADOOP-6305:
--------------------------------------------
It seems to be a separate problem: there's {{test.core.build.classes}} and
{{test.build.classes}}
The former is used to as the source of class files for the latter one. I.e.
{noformat}
<target name="jar-test" depends="compile-core-test" description="Make
hadoop-test.jar">
<copy todir="${test.build.classes}">
<fileset dir="${test.core.build.classes}"/>
</copy>
{noformat}
While it certainly seems inappropriate it ought to be addressed by a separate
JIRA such your HADOOP-6159. Does it make sense?
> 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.
