CODEWITHSUNDEEP
playframework-2.0sbtdependency-management
quantum
quantum

Reputation: 3039

Play 2.3.x libraryDependencies predefined Keys

I am exploring Play framework and SBT and I have noticed tutorials often include a set static keys such as libraryDependencies ++= Seq(javaJdbc, javaEbean, cache, javaWs).

I understand they are connected to SBT-managed dependencies and I understand how can one add such a dependency by providing maven/ivy coordinates for a given dependency but these are something different.

I would like to know more about them and my guess/understanding is they represent modules of Play framework and also specify transitive dependencies needed for correct functioning of module. However, even though I have tried to find an exhaustive list of these modules with explanations and dependencies they include, so far I haven't been able to find anything conclusive in either Play/SBT documentation.

Is there such a list? How are these static keys referred to in Play lingo? What is this concept called in SBT?

EDIT: I have found they correspond to modules in com.typesafe.play however I haven't been able to find where is the list of libraryDependencies literals from above defined.

Upvotes: 0

Views: 308

Answers (1)

Marius Soutier
Marius Soutier

Reputation: 11274

Play is actually an sbt auto-plugin. Auto-plugins allow you to define auto imports, which in turn is an object whose contents are put into scope (of your build.sbt) automatically. Play auto-imports its sub-modules and some other useful stuff.

You can find the full list in sbt-plugin/src/main/scala/PlayImport.scala.

Upvotes: 1

Related Questions