[
https://issues.apache.org/jira/browse/GIRAPH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428493#comment-13428493
]
Jakob Homan commented on GIRAPH-209:
------------------------------------
Looking good but not all the jars are tagged:
{noformat}209> ls -lh target/giraph-0.2-SNAPSHOT*.jar
target/giraph-0.2-SNAPSHOT-for-hadoop-0.23.1-jar-with-dependencies.jar
target/giraph-0.2-SNAPSHOT-javadoc.jar
target/giraph-0.2-SNAPSHOT-sources.jar
target/giraph-0.2-SNAPSHOT-tests.jar
target/giraph-0.2-SNAPSHOT.jar{noformat}
> 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-3.patch, GIRAPH-209-4.patch,
> GIRAPH-209-5.patch, GIRAPH-209-6.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
