giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-209) Include munge version in artifact name
Date Sun, 24 Jun 2012 00:34:42 GMT

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

Eli Reisman updated GIRAPH-209:
-------------------------------

    Attachment: GIRAPH-209-1.patch

this passes 'mvn verify', and my own eyeballs. appends to .jar and .tar.gz files in target/
to let user know which version was built, set by profile selection a la:

mvn -Dhadoop=<PROFILE> ...


                
> 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
>            Assignee: Eli Reisman
>            Priority: Blocker
>         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

        

Mime
View raw message