Our TravisCI build [1] tests on both 2.12.x and 2.11.x, and a few different versions of Java.
Our SBT configuration defaults to building on 2.12.6, but can be compiled with 2.11.12 by doing sbt ++2.11.12 <commands> I'm not sure if the Eclipse config files do something different, but maybe that's where your seeing things using 2.11.x? If so, we should update that to specify 2.12.6 as the default. Not sure if Eclipse has some kindof option to select scala version dependencies. Also, although our default should be 2.12.x, we do need to still maintain our 2.11.x support, since other projects we want to support (e.g. Apache Spark) do not yet work on 2.12. - Steve [1] https://travis-ci.org/apache/incubator-daffodil On 4/17/19 10:11 AM, Sloane, Brandon wrote: > While investigating a discrepency between the test results on my machine, and > those reported by our automated test system, I noticed that the test system > appears to be testing against against. 2.11.12 > > > Scala 2.12.0 was released in November 2016 (and Scala has begum release > candidates for 2.13.0). Per the release of 2.11.12 "We strongly encourage you > to upgrade to the latest stable version of Scala 2.12.x, as the 2.11.x series > is no longer actively maintained." > > > Is it deliberate that we are still on 2.11.x? > > > Brandon T. Sloane > > Associate, Services > > [email protected] | tresys.com >
