buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Assaf Arkin <ar...@intalio.com>
Subject Re: Scala 2.7.1 as default?
Date Mon, 16 Feb 2009 07:32:39 GMT
On Sun, Feb 15, 2009 at 9:37 PM, Alex Boisvert <boisvert@intalio.com> wrote:

> Buildr currently assumes Scala 2.7.1 as default by its choice of test
> libraries (scala-specs 1.2.9, scalatest 0.9.3 and scalacheck 1.3) which are
> binary-incompatible with newer versions of Scala.
>
> Would anyone object to upgrading these libraries to the latest currently
> available?   I understand we want to maintain backward compatibility in
> Buildr but if no one is still using Scala 2.7.1 then I don't think it makes
> much sense to do so.
>
> Perhaps it would make more sense to have no library defaults until things
> have stabilized?  (i.e., require users to specify versions in build.yaml)


Why can't the library default to one version and have people override it if
they so choose? That way, at least we're testing against one version, which
is better than no testing at all.

We run all the tests against one combination of versions, all other
combinations may be broken and we'll never know about them. We do use older
versions, but that's not the same as being backwards compatible (testing old
and new versions), just targeting what is probably a more common base
install.

On that note, I have Scala 2.7.3 installed via MacPorts, MacPorts is not
known for being cutting edge, which is precisely why I use it. The install
is dated Jan 22, will be over a month old before the next release of Buildr.
So +1 on upgrading to a newer version of Scala.

Assaf


>
> alex
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message