Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 21 Jun 2012 14:32:42 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1823956129.38939.1340289162800.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1829329228.35175.1340217043341.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HDFS-3549) dist tar build fails in
 hadoop-hdfs-raid project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated HDFS-3549:
-----------------------------

    Attachment: HDFS-3549.patch

Updated patch to remove need for stub findbugsExcludeFile.xml.  Also removed the dist tar config since we can inherit it from the hadoop-project-dist parent.  That simplifies the pom a bit and fixes a malformed XML issue due to the use of '2> /dev/null' which was already fixed in the parent pom.

                
> dist tar build fails in hadoop-hdfs-raid project
> ------------------------------------------------
>
>                 Key: HDFS-3549
>                 URL: https://issues.apache.org/jira/browse/HDFS-3549
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.0.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: HDFS-3549.patch, HDFS-3549.patch, HDFS-3549.patch
>
>
> Trying to build the distribution tarball in a clean tree via {{mvn install -Pdist -Dtar -DskipTests -Dmaven.javadoc.skip}} fails with this error:
> {noformat}
> main:
>      [exec] tar: hadoop-hdfs-raid-3.0.0-SNAPSHOT: Cannot stat: No such file or directory
>      [exec] tar: Exiting with failure status due to previous errors
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira