giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-209) Include munge version in artifact name
Date Mon, 06 Aug 2012 20:37:04 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jakob Homan updated GIRAPH-209:
-------------------------------

    Attachment: GIRAPH-209-8.patch

+1 except it turns out the trunk profile only works because we all happen to have those hadoop
artifacts in our local repos.  I've added the apache repos into the pom so we can pull those
artifacts in directly.  Will commit shortly.
                
> 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,
GIRAPH-209-7.patch, GIRAPH-209-8.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

        

Mime
View raw message