score:0

I used the play new to create two projects. The LDAPInterface was an interface to LDAP that we wanted to use across several applications. The Second Project was the Access manger. In the AccessManager\project\build.scala file, we structured it this way in order to use the LDAPInterface project. In eclipse, we just included the LDAPInterface in the project dependency section so we could debug. You could always compile a jar file and include that, but ... not as good if you want to drill down on project dependencies within eclipse. If we used play.Project it recognized it as a web project. If we just used Project it seemed to think it was a console application.

import sbt._
import Keys._
import play.Project._

object LDAPInterface {
  lazy val depProject = RootProject(file("../LDAPInterface"))
}

object ApplicationBuild extends Build {

  val appName         = "AccessManager"
  val appVersion      = "1.0-SNAPSHOT"

  val appDependencies = Seq(
     //Add your project dependencies here,
    javaCore,
    javaJdbc,
    javaEbean 
  )

   //   lazy val root = Project(id = "AccessManager",
    //  base = file(".")
    //).dependsOn(LDAPInterface.depProject)



  lazy val main = play.Project(appName, appVersion, appDependencies).settings(
   //  Add your own project settings here      
  ).dependsOn(LDAPInterface.depProject)
}

Related Query

More Query from same tag