Just FYI our use of munge does not prevent us from doing binary jar release. We can use classifier to release multiple Giraph jars (each built for different Hadoop).
See e.g. http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar, giraph-1.0.0-hadoop-2.0.0.jar, etc Seems to me like we don't know how long it will take to get rid of munge. Perhaps we should do this as pulling in Giraph into Maven projects would make it a lot easier for others to work with and lessen the barrier to entry? - Nitay On Apr 16, 2013, at 1:36 AM, Avery Ching <[email protected]> wrote: > Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion about > fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman, this is a > source code release, we can't really deploy jars to maven since we use munge > to support different versions of Hadoop. Once we get rid of munge, we'll be > able to do this in the future. > > Release notes: > http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html > > Release artifacts: > http://people.apache.org/~aching/giraph-1.0.0-RC3/ > > Corresponding git tag: > https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3 > > > Signing keys: > http://people.apache.org/keys/group/giraph.asc > > The vote runs for 72 hours, until Thusday 4pm PST. > > Thanks for everyone's input! > > Avery
