You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/03/17 17:32:33 UTC
[jira] [Resolved] (MAPREDUCE-3644) Snapshot builds have confusing
jar file names in share/hadoop/mapreduce in tarball
[ https://issues.apache.org/jira/browse/MAPREDUCE-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-3644.
-----------------------------------------
Resolution: Fixed
appears to have been fixed.
> 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
> Labels: bigtop
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)