change uses of throw to raise

'throw' is for escaping from control flow, whereas 'raise' is for
error conditions, e.g.

http://rubylearning.com/blog/2011/07/12/throw-catch-raise-rescue-im-so-confused/
Merge pull request #27 from aspiers/topic/use-raise-not-throw

change uses of throw to raise
allow multiple deployments
Merge pull request #28 from cloudedge/pull-req-master-d32341b46583738f3a6312b2b5f9eb2b6b3288a3

missed by Judd
add .gitignore for barclamp repos with .lock, etc
Merge pull request #29 from waynepallen/pull-req-master-770b45a2b35af829b090b82447fbc5ee900b34aa

Add .gitignore file to barclamp repo; ignore Gemfile.lock files, etc. [3/4]
convert test barclamp to engine format
replace create_proposal with call to parent
match create_proposal prototype to parent class
Merge pull request #30 from waynepallen/pull-req-master-0969e8aa3af836f5bad46694808b454961f69fe3

https://github.com/crowbar/barclamp-test/pull/30

Merged by devtool for cloudedge