hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-584) Calling shell scripts from build.xml discriminates Windows user minority.
Date Tue, 10 Oct 2006 00:38:20 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-584?page=comments#action_12441023 ] 
Konstantin Shvachko commented on HADOOP-584:

Yes, under cygwin it builds fine. But it does not if you build in a stand alone eclipse.
Which it did before the patch, and that is why I'm saying it imposes more depenecies.
I think it should not.

Here is a practical advice that solved the problem for me:
Include "C:\cygwin\bin" and "C:\Program Files\Subversion\bin" into the Path.
cygwin\bin contains sh.exe, and Subversion\bin has svn.exe, which are now
required to build hadoop.

> Calling shell scripts from build.xml discriminates Windows user minority.
> -------------------------------------------------------------------------
>                 Key: HADOOP-584
>                 URL: http://issues.apache.org/jira/browse/HADOOP-584
>             Project: Hadoop
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.7.0
>         Environment: Windows
>            Reporter: Konstantin Shvachko
> This is introduced by HADOOP-567.
> The problem is that now I cannot even build hadoop in Eclipse under Windows unless I
run it under Cygwin. 
> This is in a way the same as calling make in build.xml, which was recently fixed HADOOP-537.
> I think we should not introducing more dependencies on Cygwin just in order to show something
in Web UI.
> I also don't remember we claimed that Cygwin or anything else except for Ant is required
for Hadoop builds. 
> Is there another way of solving this?
> build.xml defines "version" property, Ant has "user.name" property. URL is not changing
very often.
> Or may be the web ui should obtain these properties in run-time.
> Or may be the Packaging is a better solution, as you guys discussed.

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


View raw message