[ 
https://issues.apache.org/jira/browse/HADOOP-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750518#comment-16750518
 ] 

Brian Grunkemeyer commented on HADOOP-15998:
--------------------------------------------

I fixed the problem about not reporting build failures first, by checking the 
exit code of the jar command.  Then, I configured our POM files to generate the 
class path using ; as a separator character on all platforms.  Maven won't 
allow us to use space as a separator character - it believes you forgot to 
specify something if you use space.
These changes help enable building on Windows in the Hadoop 3.2 release branch.

> Jar validation bash scripts don't work on Windows due to platform differences 
> (colons in paths, \r\n)
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-15998
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15998
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.2.0, 3.3.0
>         Environment: Windows 10
> Visual Studio 2017
>            Reporter: Brian Grunkemeyer
>            Assignee: Brian Grunkemeyer
>            Priority: Blocker
>              Labels: build, windows
>             Fix For: 3.3.0
>
>         Attachments: HADOOP-15998.v2.patch, HADOOP-15998.v3.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Building Hadoop fails on Windows due to a few shell scripts that make invalid 
> assumptions:
> 1) Colon shouldn't be used to separate multiple paths in command line 
> parameters. Colons occur in Windows paths.
> 2) Shell scripts that rely on running external tools need to deal with 
> carriage return - line feed differences (lines ending in \r\n, not just \n)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to