Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Mon, 25 Jun 2012 20:44:52 +0000 (UTC)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <1387413354.53152.1340657092704.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=13400873#comment-13400873 ] 

Jakob Homan commented on GIRAPH-209:
------------------------------------

* Without specifying a hadoop version the output ends up looking like:  
* When specifying the hadoop, we just end up with the value passed: giraph-0.2-SNAPSHOT-1.0-jar-with-dependencies.jar.  Maybe be more explicit name: giraph-0.2-SNAPSHOT-for-hadoop-1.0-jar-with-dependencies.jar?
* It will probably be easier to define the munge string once and then refer to it in the other locations in the file.
                
> 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