Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Fri, 22 Jun 2012 17:02:42 +0000 (UTC)
From: "Avery Ching (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <1318247758.44572.1340384562779.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1175868650.36409.1340229942682.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (GIRAPH-209) Include munge version in artifact
 name
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GIRAPH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399441#comment-13399441 ] 

Avery Ching commented on GIRAPH-209:
------------------------------------

Good idea.
                
> Include munge version in artifact name
> --------------------------------------
>
>                 Key: GIRAPH-209
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-209
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Jakob Homan
>            Priority: Blocker
>
> 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