Eclipse Oxygen3创建Maven Scala项目时构建路径多Scala库冲突

Hey there! Let's fix that annoying "multiple Scala libraries in build path" issue you're hitting as a new Scala developer in Eclipse Oxygen 3. This usually happens because two different sources are adding Scala libraries to your project—Eclipse's Scala plugin and Maven's dependency management. Here's how to sort it out step by step:

1. 定位并移除重复的Scala库 #

• Right-click your project, go to Build Path → Configure Build Path
• Switch to the Libraries tab, and you'll see at least two Scala entries:
  • One added automatically by the Eclipse Scala plugin (looks like Scala Library [2.x.x])
  • Another pulled in by Maven (usually named scala-library-x.x.x.jar under Maven Dependencies)
• Remove the Eclipse plugin-provided Scala library—we want Maven to handle all dependency management to avoid version mismatches.

2. 让Maven同步并接管依赖 #

• Right-click your project, select Maven → Update Project
• In the pop-up window, check your project, make sure Force Update of Snapshots/Releases is ticked, then click OK
• This will refresh your project to strictly follow the dependencies defined in your pom.xml, wiping out any manual library additions.

3. 验证pom.xml配置（可选但推荐） #

• Open your project's pom.xml and double-check the Scala dependencies and plugin settings match your intended Scala version. For example:

<!-- 确保scala-library版本正确 -->
<dependencies>
    <dependency>
        <groupId>org.scala-lang</groupId>
        <artifactId>scala-library</artifactId>
        <version>2.12.10</version> <!-- 替换成你用的Scala版本 -->
    </dependency>
</dependencies>

<!-- 确保scala-maven-plugin版本和Scala版本匹配 -->
<build>
    <plugins>
        <plugin>
            <groupId>net.alchim31.maven</groupId>
            <artifactId>scala-maven-plugin</artifactId>
            <version>4.5.6</version>
            <executions>
                <execution>
                    <goals>
                        <goal>compile</goal>
                        <goal>testCompile</goal>
                    </goals>
                </execution>
            </executions>
            <configuration>
                <scalaVersion>2.12.10</scalaVersion> <!-- 和scala-library版本保持一致 -->
            </configuration>
        </plugin>
    </plugins>
</build>

4. 清理并重新构建项目 #

• Right-click your project, go to Project → Clean and select your project to clear any cached build files
• Then run Run → Maven Build, enter clean install as the goal, and hit Run to let Maven rebuild the project from scratch.

After these steps, your build path should only have the Maven-managed Scala library, and the conflict should be gone. If you still run into issues, try closing and reopening Eclipse—sometimes cached data can cause odd behavior.

内容的提问来源于stack exchange，提问作者Maha