According to several howtos on Lift + sbt 0.10 [1] the jetty dependency has to have it's scope set to "jetty".

"org.mortbay.jetty" % "jetty" % "6.1.22" % "jetty"

This prevents the "eclipse" command from including the jetty jar-file in Eclipses Referenced Libraries folder.

Is it possible to add an argument to eclipse command for specifying extra scopes? Or is this achievable in some other way?

Just now I work around it by adding an extra line at the end of my build.sbt that looks like this:

libraryDependencies += "org.mortbay.jetty" % "jetty" % "6.1.22" % "test->default"

[1] http://moreindirection.blogspot.com/2011/06/migrating-to-sbt-010-lift.html

Heiko,

Apologies if this is not a bug, but following the instruction I added the following to my global .sbt:

resolvers += Classpaths.typesafeResolver

addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse" % "1.4.0-RC4")

When I launch sbt, I get the following error:

unresolved dependency: com.typesafe.sbteclipse#sbteclipse;1.4.0-RC4: not found

While sbt updates SNAPSHOT dependencies to their latest versions, eclipse with-sources doesn't seem to be pulling down the corresponding sources. Notice the date discrepancies (this is after running eclipse with-sources):

$ ll ~/.ivy2/cache/org.scalatra/scalatra_2.9.0-1/jars/scalatra_2.9.0-1-2.0.0-SNAPSHOT.jar
-rw-r--r-- 1 yang yang 362520 2011-08-18 14:48 /home/yang/.ivy2/cache/org.scalatra/scalatra_2.9.0-1/jars/scalatra_2.9.0-1-2.0.0-SNAPSHOT.jar

$ ll ~/.ivy2/cache/org.scalatra/scalatra_2.9.0-1/srcs/*
-rw-r--r-- 1 yang yang 24028 2011-07-21 11:11 scalatra_2.9.0-1-2.0.0-SNAPSHOT-sources.jar

Execution environments are the recommended way to configure the JRE/JDK used by Eclipse projects. As such, sbteclipse should support a way to do it and a SettingKey seems like the obvious approach.

If you have a multi-module project, all the dependencies must be specified for the modules:

Given:
module1
module2
module3

Module2 depends on Module1
Module3 depends on Module2 (and transitively, module1).

sbteclipse will not include module1 (and potentially its library dependencies) as part of the generated project for module3.

The only workaround is to explicitly name module1 as a dependency of Module3.

Is any support planned for scala 2.9.0 / 2.9.0-1?

with a project reference chain Sub <- Parent1 <- Parent2, both Parent1 and Parent2 should add to project Sub's build path

This probably got lost somewhere on the road ...

Using sbt 0.11 with Scala 2.9.1 with sbteclipse 1.4.0 in Ubuntu 11.04.

Attempted:

sbt "eclipse with-sources same-targets"

Got error:

[info] About to create an Eclipse project for you.
[info] Please hang on, because it might be necessary to perform one or more updates and this might take some time ...
[error] impossible to get artifacts when data has not been loaded. IvyNode = org.antlr#stringtemplate;3.2.1
[error] {file:/home/eric/src/query_face_com/make-metadata-database/}default-142448/*:update-classifiers: java.lang.IllegalStateException: impossible to get artifacts when data has not been loaded. IvyNode = org.antlr#stringtemplate;3.2.1
[error] Error running updateClassifiers task for default-142448

Workaround is to add org.antlr stringtemplate 3.2.1 manually:

// Added to build.sbt in project root
libraryDependencies ++= Seq(
"org.antlr" % "stringtemplate" % "3.2.1"
)

Hi,

I try to use your plugin for a new sbt-project. However I get always the following error:

tnzs$ sbt
[info] Loading global plugins from /home/tnzs/.sbt/plugins
[info] Loading project definition from /home/tnzs/workspace/test/project/plugins
/home/tnzs/workspace/test/build.sbt:5: error: reference to scalaVersion is ambiguous;
it is imported twice in the same scope by
import com.typesafe.sbteclipse.SbtEclipsePlugin._
and import Keys._
scalaVersion := "2.9.0"
^
/home/tnzs/workspace/test/build.sbt:5: error: reassignment to val
scalaVersion := "2.9.0"
^
[error] Type error in expression
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? q

test/build.sbt:

$ cat build.sbt
name := "My Project"

version := "1.0"

scalaVersion := "2.9.0"

libraryDependencies += "junit" % "junit" % "4.8" % "test"

plugins/build.sbt:

$ cat project/plugins/build.sbt

resolvers += Classpaths.typesafeResolver

addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse" % "1.4.0-RC2")

I used the sbt Version 0.11.0-RC0.

The default should be not the same in order to have Eclipse and sbt compile concurrently.

Hi,

If you add dependency on a compiler like this:

libraryDependencies <+= scalaVersion("org.scala-lang" % "scala-compiler" % _)

then you end up with compiler dependency being added as a normal jar to .classpath file as any other. However, we should be using the same kind of mechanism that is being used for Scala library dependency.

If one has a normal project dependency and a test->test dependency, sbteclipse creates a duplicate project dependency causing a build path error in Eclipse. Something like the following should trigger it:

lazy val foo = Project("foo", file("foo"), settings = ...)
lazy val fooTestDep = foo % "test->test"
lazy val bar = Project("bar", file("bar"), settings = ...) dependsOn(foo, fooTestDep)

A single project dependency should be created as Eclipse has no concept of a test dependency.

Tested with 1.3-RC2.

It took me a while to find out what is meant with the line
"... First add the plugin to your global plugins project ~/.sbt/plugins. Pay attention to add the resolver and libraryDependency like shown below! ..." in the README.textile.

I propose to give a little more instructions - e.g. as follows (that at least worked for me) :

• install git (anyway a good idea)
• in your homefolder create folder .sbt with subfolder plugins (mkdir ~/.sbt/plugins)
• install the plugin by
  downloading (git clone https://github.com/typesafehub/sbteclipse.git)
  and
  creating a file nambed build.sbt with that content:
  resolvers += {
  val typesafeRepoUrl = new java.net.URL("http://repo.typesafe.com/typesafe/releases")
  val pattern = Patterns(false, "[organisation]/[module]/[sbtversion]/[revision]/[type]s/module-[revision].[ext]")
  Resolver.url("Typesafe Repository", typesafeRepoUrl)(pattern)
  }

libraryDependencies <<= (libraryDependencies, sbtVersion) { (deps, version) =>
deps :+ ("com.typesafe.sbteclipse" %% "sbteclipse" % "1.1" extra("sbtversion" -> version))
}

Best Regards,
Marcus

There are situations when due to strange requirements in project generated Eclipse files need some non stanadard customization.
It would be nice to have simple extension points that would allow customization of generated Eclipse project files.

Now that there is already an Eclipse plugin for 2.8.2 and 2.9.0 the restriction to Scala 2.9 should be removed. Instead, the "success message" should make clear which Scala version was used and ask the user to pay attention to pick the matching Eclipse installation.

use the scalacoptions -encoding for the project:

scalacOptions ++= Seq("-encoding", "UTF-8", "-deprecation", "-unchecked")

When the sbt option retrieveManaged is 'true', then it would be nice for the classpaths set in .classpath to be relative to the project root. This allows the .classpath to be shared by more than one user when devs check out code.

https://gist.github.com/1345911

I try 1.2 and 1.3-RC1, both set all module's eclipse classpath to the current selected module's classpath(after "project module-name" and run "eclipse skip-root"), if the current project is root than all module's classpath set to empty.

When integration tests are added to project according to:
https://github.com/harrah/xsbt/wiki/Testing
plugin does not add them to generated .classpath.

Same thing with other custom test configurations described there.

Heiko: Renamed from "Integration test sources are not added to .classpath" because of more general solution

The url http://repo.typesafe.com/ivy-releases shown in the README did not work for me. I had to change that to http://repo.typesafe.com/typesafe/ivy-releases as advertised by the typesafe artifactory server.

I can't find a build for scala 2.9.0-1 anywhere. where can I find one? if not, can I build one myself? BTW, the repo (http://repo.typesafe.com/typesafe/releases) specified in the README does not contain any sbteclipse build at this moment.

Instead of type lambdas introduce a type alias for ValidationNEL[String, _]

renamed from "external dependency is not referenced" by hseeberger

if I have the following in: base/project/Build.scala

import sbt._
import Keys._

object MyBuild extends Build {
  lazy val a = Project("myProject", file(".")).dependsOn(uri("git://github.com/someone/dependency.git"))
}

and then I run 'sbt eclipse'

I get the following eclipse error, and I am missing 'dependency.jar' in my 'Referenced Libraries'

  Project 'myProject' is missing required Java project: 'dependency'

Given the simplicity of the plugin, does it justify the dependency on Scalaz? I think it's good practice to avoid dependencies in simple SBT plugins as it avoids situations where the user has a conflict due to different plugins requiring different versions of the dependencies.

Because of harrah/xsbt#104 we had to use updateReport.configurations instead of updateReport configuration "test". Now the sbt issue is fixed and we should give it another try.

I am tried to follow the example you gave, but it doesn't work for me:

scalatest@cm-dev-3:$ mkdir test
scalatest@cm-dev-3:$ cd test
scalatest@cm-dev-3:~/test$ sbt
Getting net.java.dev.jna jna 3.2.3 ...
:: retrieving :: org.scala-tools.sbt#boot-app
confs: [default]
1 artifacts copied, 0 already retrieved (838kB/9ms)
Getting Scala 2.8.1 (for sbt)...
:: retrieving :: org.scala-tools.sbt#boot-scala
confs: [default]
4 artifacts copied, 0 already retrieved (15296kB/16ms)
Getting org.scala-tools.sbt sbt_2.8.1 0.10.0 ...
:: retrieving :: org.scala-tools.sbt#boot-app
confs: [default]
34 artifacts copied, 0 already retrieved (6012kB/25ms)
[info] Set current project to default (in build file:/home/scalatest/.sbt/plugins/)
[info] Set current project to default (in build file:/home/scalatest/test/)

eclipse create-src skip-root
[error] java.util.NoSuchElementException: head of empty list
[error] Use 'last' for the full log.

last
[info] Set current project to default (in build file:/home/scalatest/test/)
[debug] Args = List(create-src, skip-root)
[debug] Trying to create an Eclipse project for you ...
java.util.NoSuchElementException: head of empty list
at scala.collection.immutable.Nil$.head(List.scala:386)
at scala.collection.immutable.Nil$.head(List.scala:383)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2$$anonfun$apply$13.apply(SbtEclipsePlugin.scala:193)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2$$anonfun$apply$13.apply(SbtEclipsePlugin.scala:193)
at sbt.MultiLogger.log(MultiLogger.scala:28)
at sbt.Logger$class.info(Logger.scala:72)
at sbt.AbstractLogger.info(Logger.scala:8)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2.apply(SbtEclipsePlugin.scala:193)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2.apply(SbtEclipsePlugin.scala:36)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
at sbt.Command$.process(Command.scala:91)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:72)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:72)
at sbt.State$$anon$1.process(State.scala:54)
at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:72)
at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:72)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:13)
at sbt.MainLoop$.next(Main.scala:72)
at sbt.MainLoop$.run(Main.scala:63)
at sbt.xMain.run(Main.scala:33)
at xsbt.boot.Launch$.run(Launch.scala:54)
at xsbt.boot.Launch$$anonfun$explicit$1.apply(Launch.scala:43)
at xsbt.boot.Launch$.launch(Launch.scala:68)
at xsbt.boot.Launch$.apply(Launch.scala:14)
at xsbt.boot.Boot$.runImpl(Boot.scala:24)
at xsbt.boot.Boot$.main(Boot.scala:15)
at xsbt.boot.Boot.main(Boot.scala)
[error] java.util.NoSuchElementException: head of empty list
[error] Use 'last' for the full log.

If I just run "eclipse create-src", it says it succeeded.

Somehow the options parser lost the .*

sbteclipse generates this compile target:

<classpathentry path=".target/scala-2.9.1/classes" kind="output"></classpathentry>

is it intentional to have DOTtarget and not target ?

Because different libraries are put on the test classpath, it would be nice to create separate eclipse projects for the main and test configurations. That way tests can be edited in eclipse with all the realtime feedback and typechecking goodness of the IDE.

If I have the following in my build.sbt file:

"net.liftweb" %% "lift-webkit" % liftVersion % "compile->default" withSources()

It'd be awesome if the >sbt eclipse command would attach the sources to the library jar.

renamed from "Scalaxb/generated sources?" by hseeberger

Hi,

I'm using sbteclipse on a project that uses the scalaxb plugin to turn XSD schema files into Scala source code. The resulting Eclipse project does not compile because the generated code ends up in src_generated/..., which is not exported as a source folder in the Eclipse project. Is there a recommended way to fix this? I assume I'd keep running the XSD -> .scala conversion from sbt manually, but the resulting source files would need to be included in the Eclipse build.

thanks,
Thomas

Alas, there's so much compatibility breakage in the Scala ecosystem. Thanks in advance for keeping this handy plugin up to date.

Not sure if this is an issue with the plugin or with scala-ide, here goes :

I have an SBT build definition with multiple sub projects under a root project.

I create the eclipse project files with :

eclipse same-targets with-sources

I then import the project into eclipse with "import existing projects into workspace"

I notice that the eclipse project consists of a single project, if I go in project/properties/Java Build Path/
there are two things that seem wrong :

• there are no source folders defined (in the Source tab)
• the project tab is empty

Is this expected ?

I notice that there is a .project and a .classpath that gets created for each sub project, so
it seems that the plugin at least tries to create eclipse sub projects.

Thanks

This should probably be optional, but it would be nice to configure scalac options in Eclipse from scalacOptions in SBT.

To be able to edit the SBT build definition from within Eclipse with full support, it would be useful to have a project generated for the project and project/plugins directories, too.

The new option should inhibit creation of project files in any parent folder, in order to enable convenient import-all in the case that parent projects do not contain any code (as is the case in Akka for example).

I'm interested in using sbteclipse to debug my Scala 2.9.0/sbt 0.10 project in Eclipse (3.7), but after adding the lines specified in the README to my build.sbt and running sbt update, I see the following.

> update
[info] Updating...
[warn]  module not found: com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1
[warn] ==== local: tried
[warn]   /home/yang/.ivy2/local/com.typesafe.sbteclipse/sbteclipse_2.9.0/1.1/ivys/ivy.xml
[warn]   -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]   /home/yang/.ivy2/local/com.typesafe.sbteclipse/sbteclipse_2.9.0/1.1/jars/sbteclipse_2.9.0.jar
[warn] ==== Sonatype OSS Snapshots: tried
[warn]   http://oss.sonatype.org/content/repositories/snapshots/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]   -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]   http://oss.sonatype.org/content/repositories/snapshots/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn] ==== Typesafe Repository: tried
[warn]   http://repo.typesafe.com/typesafe/releases/com.typesafe.sbteclipse/sbteclipse_2.9.0/0.10.0/1.1/ivys/sbteclipse_2.9.0-1.1.xml
[warn]   -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]   http://repo.typesafe.com/typesafe/releases/com.typesafe.sbteclipse/sbteclipse_2.9.0/0.10.0/1.1/jars/sbteclipse_2.9.0-1.1.jar
[warn] ==== public: tried
[warn]   http://repo1.maven.org/maven2/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]   -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]   http://repo1.maven.org/maven2/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn] ==== Scala-Tools Maven2 Repository: tried
[warn]   http://scala-tools.org/repo-releases/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]   -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]   http://scala-tools.org/repo-releases/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[info]
[warn] :: problems summary ::
[warn] :::: WARNINGS
[warn]          module not found: com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1
[warn]  ==== local: tried
[warn]    /home/yang/.ivy2/local/com.typesafe.sbteclipse/sbteclipse_2.9.0/1.1/ivys/ivy.xml
[warn]    -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]    /home/yang/.ivy2/local/com.typesafe.sbteclipse/sbteclipse_2.9.0/1.1/jars/sbteclipse_2.9.0.jar
[warn]  ==== Sonatype OSS Snapshots: tried
[warn]    http://oss.sonatype.org/content/repositories/snapshots/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]    -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]    http://oss.sonatype.org/content/repositories/snapshots/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn]  ==== Typesafe Repository: tried
[warn]    http://repo.typesafe.com/typesafe/releases/com.typesafe.sbteclipse/sbteclipse_2.9.0/0.10.0/1.1/ivys/sbteclipse_2.9.0-1.1.xml
[warn]    -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]    http://repo.typesafe.com/typesafe/releases/com.typesafe.sbteclipse/sbteclipse_2.9.0/0.10.0/1.1/jars/sbteclipse_2.9.0-1.1.jar
[warn]  ==== public: tried
[warn]    http://repo1.maven.org/maven2/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]    -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]    http://repo1.maven.org/maven2/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn]  ==== Scala-Tools Maven2 Repository: tried
[warn]    http://scala-tools.org/repo-releases/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.pom
[warn]    -- artifact com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1!sbteclipse_2.9.0.jar:
[warn]    http://scala-tools.org/repo-releases/com/typesafe/sbteclipse/sbteclipse_2.9.0/1.1/sbteclipse_2.9.0-1.1.jar
[warn]          ::::::::::::::::::::::::::::::::::::::::::::::
[warn]          ::          UNRESOLVED DEPENDENCIES         ::
[warn]          ::::::::::::::::::::::::::::::::::::::::::::::
[warn]          :: com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1: not found
[warn]          ::::::::::::::::::::::::::::::::::::::::::::::
[info]
[info] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
[error] Incomplete tasks (run 'last <task>' for the full log):
[error]   {file:/home/yang/pod/sales/web/}default/*:update: sbt.ResolveException: unresolved dependency: com.typesafe.sbteclipse#sbteclipse_2.9.0;1.1: not found
[error] Total time: 20 s, completed Jul 12, 2011 11:33:12 PM

I went through your blog post and got the following runtime exception:

[debug] Args = List(create-src, skip-root)
[debug] Trying to create an Eclipse project for you ...
java.util.NoSuchElementException: head of empty list
at scala.collection.immutable.Nil$.head(List.scala:386)
at scala.collection.immutable.Nil$.head(List.scala:383)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2$$anonfun$apply$13.apply(SbtEclipsePlugin.scala:193)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2$$anonfun$apply$13.apply(SbtEclipsePlugin.scala:193)
at sbt.MultiLogger.log(MultiLogger.scala:28)
at sbt.Logger$class.info(Logger.scala:72)
at sbt.AbstractLogger.info(Logger.scala:8)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2.apply(SbtEclipsePlugin.scala:193)
at com.typesafe.sbteclipse.SbtEclipsePlugin$$anonfun$2.apply(SbtEclipsePlugin.scala:36)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply$2.apply(Command.scala:61)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply$3.apply(Command.scala:63)
at sbt.Command$.process(Command.scala:91)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:72)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(Main.scala:72)
at sbt.State$$anon$1.process(State.scala:54)
at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:72)
at sbt.MainLoop$$anonfun$next$1.apply(Main.scala:72)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:13)
at sbt.MainLoop$.next(Main.scala:72)
at sbt.MainLoop$.run(Main.scala:63)
at sbt.xMain.run(Main.scala:33)
at xsbt.boot.Launch$.run(Launch.scala:54)
at xsbt.boot.Launch$$anonfun$explicit$1.apply(Launch.scala:43)
at xsbt.boot.Launch$.launch(Launch.scala:68)
at xsbt.boot.Launch$.apply(Launch.scala:14)
at xsbt.boot.Boot$.runImpl(Boot.scala:24)
at xsbt.boot.Boot$.main(Boot.scala:15)
at xsbt.boot.Boot.main(Boot.scala)
[error] java.util.NoSuchElementException: head of empty list

For many projects, one wants to configure the plugin in the build file once instead of every user doing it in their own machine. The documentation should mention how to do this.

Following the instructions in https://github.com/typesafehub/sbteclipse#readme I get the following:

eclipse create-src skip-root
[error] Not a valid key: eclipse (similar: deliver, clean)
[error] eclipse create-src skip-root
[error] ^

eclipse
[error] Not a valid command: eclipse (similar: help, alias)
[error] Not a valid project ID: eclipse
[error] Not a valid configuration: eclipse
[error] Not a valid key: eclipse (similar: deliver, clean)
[error] eclipse
[error] ^

Happens on Windows 7 (64bit) with Java 1.6.0_26 (64bit)