+1, much better than having a new PR each time to fix something for scala-2.11 every time a patch breaks it.
Thanks, Hari Shreedharan > On Oct 9, 2015, at 11:47 AM, Michael Armbrust <mich...@databricks.com> wrote: > > 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. > > +1 > > It also does not seem that expensive to test only compilation for Scala 2.11 > on PR builds.
