How about just fixing the warning? I get it; it doesn't stop this from happening again, but still seems less drastic than tossing out the whole mechanism.
On Fri, Oct 9, 2015 at 3:18 PM, Iulian Dragoș <iulian.dra...@typesafe.com> wrote: > Sorry for not being clear, yes, that's about the Sbt build and treating > warnings as errors. > > Warnings in 2.11 are useful, though, it'd be a pity to keep introducing > potential issues. As a stop-gap measure I can disable them in the Sbt build, > is it hard to run the CI test with 2.11/sbt? > > iulian > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
