Revert "[maven-release-plugin] prepare for next development iteration"

This reverts commit 216b473df0d6912f4905204402cfe04568e0560c.
Revert "[maven-release-plugin] prepare release v0.8.1-incubating"

This reverts commit 7e5564cc788c33a3048914d61e90eff88b1a3903.
Merge pull request #248 from colorant/branch-0.8

Fix POM file for mvn assembly on hadoop 2.2 Yarn

This is the fix for maven YARN build on hadoop 2.2
Updating CHANGES and one fix from last merge
Add missing dependencies
Small fix from prior commit
Merge pull request #250 from pwendell/master

README incorrectly suggests build sources spark-env.sh

This is misleading because the build doesn't source that file. IMO
it's better to force people to specify build environment variables
on the command line always, like we do in every example, so I'm
just removing this doc.
(cherry picked from commit d2efe13574090e93c600adeacc7f6356bc196e6c)

Signed-off-by: Patrick Wendell <pwendell@gmail.com>
[maven-release-plugin] prepare release v0.8.1-incubating
[maven-release-plugin] prepare for next development iteration
Revert "[maven-release-plugin] prepare for next development iteration"

This reverts commit 7ca53692c821ead3a50520fe51e229d9fc1f856d.
Revert "[maven-release-plugin] prepare release v0.8.1-incubating"

This reverts commit 909a9e4d11eccea03980a8ed7ba7f9f27c68e33a.
Small bug fix in YARN build patch
[maven-release-plugin] prepare release v0.8.1-incubating
[maven-release-plugin] prepare for next development iteration
Version updates not handled by maven release plug-in
Force pseudo-tty allocation in spark-ec2 script.

ssh commands need the -t argument repeated twice if there is no local
tty, e.g. if the process running spark-ec2 uses nohup and the parent
process exits.
Merge pull request #271 from ewencp/really-force-ssh-pseudo-tty-0.8

Force pseudo-tty allocation in spark-ec2 script.

ssh commands need the -t argument repeated twice if there is no local
tty, e.g. if the process running spark-ec2 uses nohup and the parent
process exits.

Without this change, if you run the script this way (e.g. using nohup from a cron job), it will fail setting up the nodes because some of the ssh commands complain about missing ttys and then fail.

(This version is for the 0.8 branch. I've filed a separate request for master since changes to the script caused the patches to be different.)