Eli Reisman created GIRAPH-707:
----------------------------------
Summary: Giraph could probably support Hadoop 2.0.x-alpha line
using a single build profile
Key: GIRAPH-707
URL: https://issues.apache.org/jira/browse/GIRAPH-707
Project: Giraph
Issue Type: Improvement
Reporter: Eli Reisman
Priority: Trivial
The title says it all. Other that switching the "hadoop.version" Maven property
setting, these basically all do the same stuff from the build perspective and
are starting to cluster up our POM.xml
On the other hand, this adds verbosity and another layer of complexity to our
build command line. Instead of:
{code}mvn -Phadoop_2.0.3 clean install{code}
we would have:
{code}mvn -Dhadoop.version=2.0.3-alpha -Phadoop_2_alpha clean install{code}
as the user would still need to pick out a Hadoop-2.0.x to build against.
Alternately, we could just make the decision "its an alpha release" and always
point -Phadoop_2_alpha to the newest release. This could cause some confusion
among users during a new Hadoop-2.0.x release, but then all Hadoop-2.x builds
would look like:
{code}mvn -Phadoop_2_alpha clean install{code}
If anyone cares, please post your opinions or a patch according to your
particular inclination. This will be an easy fix, whatever we decide.
Or we can do nothing. Thats fine too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
