Versioning jars and other artifacts

I think Scala's getting to the point where distributions may want to
provide multiple Scala versions at the same time, much like Ubuntu or
MacPorts can have Python 2.4, 2.5 and 2.6 installed at the same time.

I know I'm starting to want this for my MacPorts' system so I can use
different compilers for different projects, some of which are on 2.7 and
some moving to 2.8, or I want a scala shell in one of the versions.

That said, I think it would be easier to deploy if the Scala
distribution starts to put the major and minor version number in jars,
so instead of scala-library.jar we would have scala-library-2.8.jar.
The wrapper shell scripts would have to be updated.

I realize this is getting close to the ABI issue for jars compiled with
different Scala versions. Maybe we put the full version number in the
jar's, just like Spring does:

$ cd spring-framework-3.0.0.RELEASE
$ find -name \*jar
./dist/org.springframework.aop-3.0.0.RELEASE.jar
./dist/org.springframework.asm-3.0.0.RELEASE.jar

Blair