[ 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-4.patch added the ${basedir}/target/... to line 654 of the top-level POM.xml so that when Eugene's GIRAPH-212 patch gets committed to fix secure version, this will integrate smoothly. Passes all mvn verify, seems to work with -Dhadoop=... and -P profile options. So this seems to be the right patch to get this closed out at this point. > 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 > > > 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