[ https://issues.apache.org/jira/browse/GIRAPH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400984#comment-13400984 ]
Eli Reisman commented on GIRAPH-209: ------------------------------------ the munge string I am using is just the ${hadoop} var thats already there, if the user chooses not to set it, it uses the standard naming scheme as it is. I assumed if you know to set -Dhadoop=... then you know what its for or why. What should I use as a sub? > Include munge version in artifact name > -------------------------------------- > > Key: GIRAPH-209 > URL: https://issues.apache.org/jira/browse/GIRAPH-209 > Project: Giraph > Issue Type: Bug > Affects Versions: 0.2.0 > Reporter: Jakob Homan > Assignee: Eli Reisman > Priority: Blocker > Fix For: 0.2.0 > > Attachments: GIRAPH-209-1.patch > > > Right now, regardless of what munge parameter is passed in, the result jar > and .tar.gz is just called giraph, meaning one can't know if one has the > munged version one wants or even what one really has. The artifacts should > include the munging identifier. -- 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