[ https://issues.apache.org/jira/browse/HBASE-17352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob reopened HBASE-17352: ------------------------------- I'm seeing this same failure on branch-1, can we apply this fix to all active development branches? > Fix hbase-assembly build with bash 4 > ------------------------------------ > > Key: HBASE-17352 > URL: https://issues.apache.org/jira/browse/HBASE-17352 > Project: HBase > Issue Type: Bug > Reporter: Junegunn Choi > Assignee: Junegunn Choi > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-17352.patch > > > hbase-assembly fails to build with bash 4. > {noformat} > [DEBUG] Executing command line: [env, bash, -c, cat > maven-shared-archive-resources/META-INF/NOTICE \ > `find > /Users/jg/github/hbase/hbase-assembly/target/dependency -iname NOTICE -or > -iname NOTICE.txt` \] > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec > (concat-NOTICE-files) on project hbase-assembly: Command execution failed. > Process exited with an error: 1 (Exit value: 1) -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (concat-NOTICE-files) on > project hbase-assembly: Command execution failed. > {noformat} > The error is caused by the trailing backslash in the bash command for > {{concat-NOTICE-files}}. You can see the behavioral difference between bash 3 > and 4 with the following snippet. > {code} > $ # Using bash 3 > $ /bin/bash -c 'cat <(echo foo) \' && echo good || echo bad > foo > good > $ # Using bash 4 > $ /usr/local/bin/bash -c 'cat <(echo foo) \' && echo good || echo bad > foo > cat: \: No such file or directory > bad > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)