We just published parts of our library (Mango) which is a Scala wrapper around Google Guava common libraries for Java.
The library currently depends on Google Gauva 14.0, but we would like to add support for other versions as well.
Is there a way in sbt, a build-automation tool for Scala and Java projects, to create maven like profiles, where each profile compiles against a different version of the respective Guava dependency, so we can include it in the continuous integration test matrix?
Ideally, it should be possible to call sbt with something like:
sbt test guava:14.0 sbt test guava:13.0 ...