sbt-eclipse generates project definition for wrong project

I use sbt-eclipse 2.4.0

~/.sbt/0.13/plugins$ cat build.sbt
addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse-plugin" % "2.4.0")

resolvers += "Sonatype snapshots" at "http://oss.sonatype.org/content/repositories/snapshots/"

And have the following build.sbt:

import com.typesafe.sbt.SbtAtmosPlay.atmosPlaySettings

libraryDependencies ++= Seq(
  "org.webjars" %% "webjars-play" % "2.2.0",
  "org.webjars" % "angularjs" % "1.2.0-rc.3",
  "org.webjars" % "bootstrap" % "2.3.2"
)

name := "ImageMaster"

version := "1.0-SNAPSHOT"

play.Project.playScalaSettings

atmosPlaySettings

val ImageMaster = project.in(file("."))
  .aggregate(ImageCommon).dependsOn(ImageCommon)

lazy val ImageCommon = RootProject(file("../ImageCommon/"))

ImageCommon is a library project which is on the same directory level as ImageMaster as it is used across many different projects.

When I run the eclipse task, it will generate the eclipse files for ImageCommon. I need to uncomment the the line with ".aggregate(ImageCommon).dependsOn(ImageCommon)", run the eclipse task and add the ImageCommon project within eclipse to the build path to get a correctly compiling project.

Start with the supplied build.sbt and the eclipse task, reproducing the generated project definition for ImageMaster and ImageCommon. Compare the generated Eclipse files with the project that should be selected, then verify the result with the aggregate and dependsOn settings enabled without requiring the workaround.