Cedrik, The approach I demonstrated will not change the project version. In the example below it is 1.0.0-SNAPSHOT and for SLF4J it could be 1.6.2 or 1.7.0 or whatever. Only the artifactID will be "enriched" by suffixing with the Scala version. This approach was introduced by the SBT build tool which is the de-facto standard in the Scala community. There is a nice feature which lets you just declare the plain artifactID and SBT will calculate the enriched one for you depending on what Scala version you build against. Therefore this is definitely the way to go. While it might maybe be possible to tweak SBT to use your approach, that's just not what Scala people are used to. Heiko On Wednesday, September 8, 2010, Cédrik LIME <2010@cedrik.fr> wrote:

Don't you want to name your artefact:        scala-profiles-demo-1.0-<scala_version>.jar ? That way, maven users simply need to use the <classifier> tag in their pom's <dependency>; no need to change the SLF4J|S <version>!

       Cédrik

Le 08/09/2010 08:33, Heiko Seeberger a écrit :

And here comes the solution: http://github.com/hseeberger/scala-profiles-demo

Run Maven twice: 1. mvn install 2. mvn -Pscala-2.7.7 install

You wil get exactly what we need: ./scala-profiles-demo_2.7.7 ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/maven-metadata-local.xml ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/scala-profiles-demo_2.7.7-1.0-SNAPSHOT.jar ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/scala-profiles-demo_2.7.7-1.0-SNAPSHOT.pom ./scala-profiles-demo_2.7.7/maven-metadata-local.xml ./scala-profiles-demo_2.8.0 ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/maven-metadata-local.xml ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/scala-profiles-demo_2.8.0-1.0-SNAPSHOT.jar ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/scala-profiles-demo_2.8.0-1.0-SNAPSHOT.pom ./scala-profiles-demo_2.8.0/maven-metadata-local.xml

Heiko

-- Heiko Seeberger Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org