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 Sat, 04 Aug 2012 00:01:02 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-6.patch

fixed, tested on a number of profiles, seems to work fine. Now the -Dhadoop=... option is
not the way to select a profile, the -P option is again functional using the proper profile
names like:

mvn -Phadoop_trunk clean package

etc.

                
> 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

        

Mime
View raw message