[
https://issues.apache.org/jira/browse/GIRAPH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402445#comment-13402445
]
Jakob Homan commented on GIRAPH-209:
------------------------------------
Looking good.
* Values are coming out with "for hadoop" with just "for, eg
giraph-0.2-SNAPSHOT-for-1.0-bin.tar.gz
* Rather than putting default into the name we can explicitly call out the
value (0.203)
* It looks like the munged jar isn't getting named.
> 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
> Labels: patch
> Fix For: 0.2.0
>
> Attachments: GIRAPH-209-1.patch, GIRAPH-209-2.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
