Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Plugin for sbt to create Eclipse project definitions

Subscribe to updates I use sbteclipse

Statistics on sbteclipse

Number of watchers on Github 689
Number of open issues 79
Average time to close an issue 2 months
Main language Scala
Average time to merge a PR 11 days
Open pull requests 5+
Closed pull requests 12+
Last commit over 1 year ago
Repo Created over 8 years ago
Repo Last Updated over 1 year ago
Size 1.08 MB
Organization / Authorsbt
Page Updated
Do you use sbteclipse? Leave a review!
View open issues (79)
View sbteclipse activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating sbteclipse for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

sbteclipse Build Status

Plugin for sbt to create Eclipse project definitions. Please see below for installation details and the Documentation for information about configuring sbteclipse. Information about contribution policy and license can be found below.

For sbt 0.13 and up

  • Add sbteclipse to your plugin definition file (or create one if doesn't exist). You can use either:

    • the global file (for version 0.13 and up) at ~/.sbt/0.13/plugins/plugins.sbt
    • the project-specific file at PROJECT_DIR/project/plugins.sbt

For the latest version:

addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse-plugin" % "5.2.4")
  • In sbt use the command eclipse to create Eclipse project files

    > eclipse

  • In Eclipse use the Import Wizard to import Existing Projects into Workspace

Multi ScalaVersion support

Since Scala IDE 4.0 multiple scala versions are supported in a single eclipse workspace. The Scala IDE uses by default the highest supported scala version, 2.11 since Scala IDE 4.0 and 2.12 since Scala IDE 4.6. The default can be overwritten at workspace level or at project level. The latter is stored in the file .settings/org.scala-ide.sdt.core.prefs. This file can be generated with sbteclipse.

For sbteclipse 5.2.5 and up

Given Xi.Yi is the default Scala installation version of your Scala IDE, and Xp.Yp.Zp is the targetted scala version of your project, you add following in your sbt build file:

  EclipseKeys.defaultScalaInstallation := "Xi.Yi" // "2.12" is the default
  ScalaVersion := "Xp.Yp.Zp"

In case Xp.Yp < Xi.Yi, the lower scala.compiler.installation is configured at project level.

When you're using ScalaIDE-4.6.0 up to 4.7._ (until a new major scala version is the default), and x.y.z matches with one of the pre-installed scala compilers in the IDE, it should work fine out of the box.

For sbteclipse 4.0. up to 5.2.4

In case Xp.Yp = 2.10, the lower scala.compiler.installation is configured at project level.

When you're using ScalaIDE-4.0 up to 4.5._, and x.y.z matches with one of the pre-installed scala compilers in the IDE, it should work fine out of the box.

Contribution policy

Contributions via GitHub pull requests are gladly accepted from their original author. Before we can accept pull requests, you will need to agree to the Typesafe Contributor License Agreement online, using your GitHub account - it takes 30 seconds.


This code is open source software licensed under the Apache 2.0 License. Feel free to use it accordingly.



Maintainers must run git tag to tag a release. The release can then be pushed to bintray with sbt ^publish.

sbteclipse open issues Ask a question     (View All Issues)
  • about 3 years sbt eclipe is not valid command
  • over 3 years eclipse project file generator
  • over 3 years global sbteclipse cannot be resolved
  • over 3 years Need a way to automatically add org.eclipse.pde.PluginNature to an Eclipse project
  • over 3 years sbt-eclipse,sbt-assembly plugin issue: scala-spark-sbt-plugins
  • over 3 years sbteclipse-plugin;4.0.0: not found
  • over 3 years Rename sbteclipse-plugin artefact name to sbt-eclipse
  • over 3 years Error in Scala compiler for project generated with sbteclipse with space in its name
  • over 3 years Manage Scopes Settings correctly
  • over 3 years Repository for sbteclipse plugin
  • almost 4 years EclipseKeys.eclipseOutput isn't used for play generated routes
  • almost 4 years NoSuchMethodError with sbt 0.13.9 and Play 2.2.6 and plugin version 4.0.0
  • almost 4 years 4.0.0 plugin does not create directories on OS X
  • about 4 years java.lang.IllegalStateException: Undefined setting 'eclipseSkipProject' (for RootProject)
  • about 4 years add recommendations for multiprojects and crossprojects
  • about 4 years Wiki not updated after 2.5.0
  • about 4 years Can't use EclipseKeys unqualified when using sbteclipse is global plugin
  • over 4 years useProjectID does not work in multi-project settings
  • over 4 years Eclipse per-source folder output directory
  • over 4 years Problem with classpath dependencies with dependsOn
  • over 4 years Changelog / Release Notes?
  • over 4 years sbteclipse doesn't support scala compiler version setting
  • over 4 years `activator eclipse` command shows sbt.ResolveException:
  • over 4 years Allow custom project-specific settings (such as formatter.rewriteArrowSymbols)
  • over 4 years `def setting` is in a private object on master, how to access?
  • over 4 years Project's flavour should automatically detected, instead of being hardcoded in the settings
  • over 4 years dependsOn doesn't work with CrossProject
  • over 4 years issue installing sbteclipse
  • over 4 years relativizeLibs is ignored?
  • over 4 years SbtEclipse does not include sbt related jars, build.scala thus shows a lot of unresolved type errors
sbteclipse open pull requests (View All Pulls)
  • Use source artifacts that come with update report
  • Move defaults to globalSettings (fix #296), try #2
  • Switch to scalaz 7.2
  • Update sbt link in README
  • Support Scala 2.11
sbteclipse questions on Stackoverflow (View All Questions)
  • sbt.Resolve Exception : unresolved dependency: com.typesafe.sbteclipse#sbteclipse-plugin 2.4.0 not found
  • sbteclipse not adding generated source folders to java build path?
  • How can I show a source directory to sbteclipse without adding it to the Compile or Test configuration
  • sbteclipse can not use eclipse command
  • Installing sbteclipse
  • sbteclipse main and test resources overlapping
  • sbteclipse 2.4.0 doesn't work with sbt 0.13.1 and Scala 2.10.3, on Fedora 20 XFCE
  • Failed javadoc downloads with sbteclipse when using with-source=true
  • how to add sbteclipse plugin in eclipse
  • eclipse gives error on start up after adding sbteclipse plugin
  • Running sbt results in "com.typesafe.sbteclipse#sbteclipse;1.4.0: not found"
  • Global sbteclipse plugin not found/loaded
  • Using classpathTransformerFactories in sbteclipse plugin to exclude Scala library?
  • how to get sbteclipse to work with unmanagedBase in Provided scope?
  • Configuring SbtEclipse to get the right value for lib_managed
  • sbteclipse additional source folders
  • scalatra probem when running ./sbt: sbt.ResolveException: unresolved dependency: com.typesafe.sbteclipse#sbteclipse-plugin;2.1.1: not found
  • How to tell sbteclipse to ignore src/main/java?
  • Trouble using sbteclipse
  • sbteclipse doesn't create a Scala project by default?
  • How to get sbteclipse working with Scala 2.9
  • sbteclipse: Managed dependencies not found by eclipse
  • Creating Scala Project with Eclipse, sbteclipse -- directory layout
  • How and where to add an sbteclipse task?
  • SBT + Lift - Not being able to build with sbteclipse
  • How to add sbteclipse plugin to SBT 0.10.x
sbteclipse list of languages used
Other projects in Scala