Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
Progress commit for review
move conf initialization to TestEnvironment
Refactored TestEnvironment to use hadoop Paths
Added 'Add' local operation and test
removed erroneously added eclipse plugin
remove unnecessary 'extends MustMatcher' from tests
Created a separate trait called SparkEnvironment for SparkContext creation
- This trait can be mixed in by only those tests that need a Spark context
Add localMin on rasters.
Add max on rasters.
Add mask on raster.
Another attempt at SparkContext creation in tests.
SparkEnvironment then looks like this
- a myIt that users call instead of it. myIt ends up calling it
- a setup/tearDown that actually creates and frees the mutable context variable
The second point is why I don't like this too much as users need to call this
in every suite that uses SparkContext
minor change: organize imports