Support for embedding Pig scripts in Java test files

Uses a neat trick presented by Adrian Walker in this blog post: http://www.adrianwalker.org/2011/12/java-multiline-string.html

With this the pig scripts can be embedded directly in the Java files as javadoc comments on class fields.  Tests are much easier to work with this way.

I removed all pig test files for the util tests to demonstrate.

Also added an ant target "eclipse" which generates some eclipse files.  It figures out what the paths should be based on the environment.  This fixes an issue where paths would be incorrect when working in another repo.
Rename test variables
Merge with linkedin master
Add tools dependency
Fix resolution of tools jar
Fix testng path
Add classes to tools resolver for mac os
Sessionize should allow long for time as well
Merge pull request #35 from evionkim/master

Created package sampling/ Added SampleByKey UDF
Remove comments in pig script
Add source of multiline java code
Merge pull request #39 from matthayes/master

Support for embedding multiline Pig scripts in Java test files
Cleanup tests

Moved pig code in Java files for stats and urls.

Also removed ApplyQuantiles since can compute more easily through Enumerate and dividing by size.
More test cleanup
Rename datafu.pig.numbers to datafu.pig.random
Cleanup tests
Merge pull request #41 from matthayes/master

Test cleanup
Improve output schemas for Quantile and StreamingQuantile

These two UDFs were inconsistent in how they named the output quantiles.  The convention of StreamingQuantile actually made more sense, so standardizing on that.

The convention:
* If you request specific quantiles, the output quantiles will be named based on this.  For example, 0.5 yields quantile_0_5.
* If you request n quantiles, then the output quantiles will be labeled 0..(n-1).  For example, 3 yields quantile_0, quantile_1, and quantile_3.

Previously if you requested 3 for Quantile you would get 0_0, 0_5, and 1_0.  The problem with this convention is that if you requested many quantiles, e.g. 1000, it's hard to know what the names will be.  But if you request 1000 you can at least be sure that quantile_499, quantile_500, etc. exist.

Also added test cases which check the output schema by using FOREACH..GENERATE on the names.
Merge pull request #42 from matthayes/master

Make Quantile output schemas consistent with StreamingQuantile
README update