Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Mon, 9 Jan 2012 20:09:40 +0000 (UTC)
From: "Andrew Bayer (Created) (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <982247871.22726.1326139780074.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-3644) Snapshot builds have confusing
 jar file names in share/hadoop/mapreduce in tarball
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Snapshot builds have confusing jar file names in share/hadoop/mapreduce in tarball
----------------------------------------------------------------------------------

                 Key: MAPREDUCE-3644
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3644
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: build, mrv2
    Affects Versions: 0.23.0
            Reporter: Andrew Bayer


If you build a Hadoop tarball with a non-release version, the moduleSet used in hadoop-assemblies/src/main/resources/assemblies/hadoop-mapreduce-dist.xml results in jar files going into share/hadoop/mapreduce with unique snapshot versions - i.e., the timestamp they were built. This isn't an issue in release builds. It can be fixed by adding " <outputFileNameMapping>${module.artifactId}-${project.version}${dashClassifier?}.${module.extension}</outputFileNameMapping>" to the binaries tag of the moduleSet.

--
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