Play Framework core dependency management/exclusion

Question

We are using play 2.1.1 (scala) and in some efforts to tie down our dependencies, have found there are several older deps being loaded in directly by the play framework.

specifically, the oauth.signpost brings in http-components 4.0 ( and in turn commons-codec 1.3 ) whereas we have other dependencies on http-componts 4.1 and commons-codec 1.6

the documentation seems pretty sparse in this area - at least in the older play 1.2.x the dependencies.yml was somewhat more explicit, but i cant find any references for the current 2.1.x release.

i'd hate to have to futz with the framework's Build.scala in ${PLAY2_HOME}/framework/project to remove the dependency ( we will never need oauth.signpost in this particular app ), but so far this seems like the only way.

any pointers?

(edit: i also came across this: Play Framework 2.1 Remove a core dependency which is related to a specific transitive dependency, what i'd prefer to be able to do is remove the whole explicit dependency from the core framework )

ndeverge ndeverge · Accepted Answer · 2013-04-09T08:15:34

I don't know how to exclude a core dependency, but you may try to exclude the transitive dependencies in your Build.scala file:

val appDependencies = Seq(
     ...
     ("oauth.signpost" % "signpost-commonshttp4" % "1.2.1.2") .exclude("org.apache.httpcomponents", "httpclient")
    )

or use the intransitive() method:

val appDependencies = Seq(
     ...
     ("oauth.signpost" % "signpost-commonshttp4" % "1.2.1.2") .intransitive()
    )

It is not the perfect solution, but it may help you.

Play Framework core dependency management/exclusion

2 Answers