[DISCUSS] Stop support for non-packaged i.e. developer build single-node installs

2012-01-18 Thread Arun C Murthy
Folks, Somewhere between MR-279 and mavenization we have broken the support for allowing _developers_ to run single-node installs from the non-packaged 'build' i.e. ability to run single-node clusters without the need to use a tarball/rpm etc. (I fully suspect MR-279 is blame as much as

Re: [DISCUSS] Stop support for non-packaged i.e. developer build single-node installs

2012-01-18 Thread Tom White
Arun, There are instructions on how to run 0.23/trunk from the dev tree here: http://wiki.apache.org/hadoop/HowToSetupYourDevelopmentEnvironment#Run_HDFS_in_pseudo-distributed_mode_from_the_dev_tree

Re: [DISCUSS] Stop support for non-packaged i.e. developer build single-node installs

2012-01-18 Thread Ravi Prakash
I think also at issue is the maven build system. I don't know if its intended, but if I change a single .java file, mvn -Pdist -P-cbuild -Dmaven.javadoc.skip -DskipTests install runs a TON of stuff It takes a 1m 29s to finish even if there are NO changes anywhere. I doubt this is how it should

Re: [DISCUSS] Stop support for non-packaged i.e. developer build single-node installs

2012-01-18 Thread Eric Yang
Single node developer build may be supported independently from package installed builds. There are multiple ways to achieve this. The current method is using shell script to support different deployment conditions. This is a awkward and inefficient way to maintain compatibility to support