[ http://issues.apache.org/jira/browse/HADOOP-537?page=comments#action_12435600 ] Doug Cutting commented on HADOOP-537: -------------------------------------
We shouldn't need a clean-X target for every compile-X target, since compile-X targets should place things in the build directory and the build directory should be removed by the single clean target. We should also try not to clutter the top-level build.xml. If a separate clean-X target is required for productive development in some subtree, then it should be placed in a separate build.xml or Makefile in that source subtree. It can then remove appropriate items from the top-level build directory. But, ideally, the top-level 'clean' target should be able to remove all generated items by simply removing the top-level build directory. > clean-libhdfs target of build.xml does not work on windows > ---------------------------------------------------------- > > Key: HADOOP-537 > URL: http://issues.apache.org/jira/browse/HADOOP-537 > Project: Hadoop > Issue Type: Bug > Components: libhdfs > Affects Versions: 0.6.0 > Environment: Windows > Reporter: Konstantin Shvachko > > It produces the following: > BUILD FAILED > Hadoop\build.xml:496: Execute failed: java.io.IOException: CreateProcess: > make clean error=2 > Besides, I would propose to have clean-* target for every compile-* target in > build.xml. > Some people probably don't build libhdfs or contrib, so why should they clean > it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
