> As it does not feel good to have two jars of the same lib in the path, I
> was wondering what is the standard behaviour for that case. Remove the
> Eclipse plugin's scala lib container from the path ?
It's a bit odd to have one Scala lib directly in the project for the SDT
and one other in the Maven dependencies. However, if you use the latest
snapshots of both, they should be compatible.
This is my Maven-plug config and dependency:
<plugin>
<groupId>org.scala-tools</groupId>
<artifactId>maven-scala-plugin</artifactId>
<configuration>
<charset>UTF-8</charset>
<encoding>UTF-8</encoding>
<jvmArgs>
<jvmArg>-Xms64m</jvmArg>
<jvmArg>-Xmx1g</jvmArg>
</jvmArgs>
<sourceDir>src/main/java</sourceDir>
</configuration>
</plugin>
`maven-scala-plugin' deduces the Scala-lib and Scala-compiler version
from the `scala-library' dependency, which looks like this:
<dependency>
<groupId>org.scala-lang</groupId>
<artifactId>scala-library</artifactId>
<version>${scalaVersion}</version>
</dependency>
where `scalaVersion' is a property:
<properties>
...
<scalaVersion>2.8.0-SNAPSHOT</scalaVersion>
...
</properties>
These are the relevant repositories:
<repositories>
<repository>
<id>org.scala-tools.repository.releases</id>
<name>Scala-Tools Releases</name>
<url>
http://scala-tools.org/repo-releases</url>
</repository>
<repository>
<id>org.scala-tools.repository.snapshots</id>
<name>Scala-Tools Snapshots</name>
<url>
http://scala-tools.org/repo-snapshots</url>
</repository>
</repositories>
This setup works fine for me, both in Eclipse and on the command line
with Maven.
Hope this helps,
---Ph.
