good question ;)
This is due to your Enumeratees which are in JSON object, Julien :D

I wondered if I should move them but it would have broken the API.
So first step was to create module like that and see if we keep this dep on
iteratees which is a bit superficial.
But anyway, this doesn't bring unwanted deps to people, this is pure
scala...

On Fri, Feb 22, 2013 at 12:04 PM, Julien Richard-Foy <
notifications@github.com> wrote:

> In framework/project/Build.scala:
>
> > +        )
> > +    ).settings(com.typesafe.sbtscalariform.ScalariformPlugin.defaultScalariformSettings: _*)
> > +
> > +    lazy val JsonProject = Project(
> > +        "Play-Json",
> > +        file("src/play-json"),
> > +        settings = buildSettingsWithMIMA ++ Seq(
> > +            previousArtifact := Some("play" % {"play-json_"+previousScalaVersion} % previousVersion),
> > +            libraryDependencies := jsonDependencies,
> > +            publishTo := Some(playRepository),
> > +            scalacOptions ++= Seq("-encoding", "UTF-8", "-Xlint","-deprecation", "-unchecked", "-feature"),
> > +            publishArtifact in packageDoc := buildWithDoc,
> > +            publishArtifact in (Compile, packageSrc) := true
> > +        )
> > +    ).settings(com.typesafe.sbtscalariform.ScalariformPlugin.defaultScalariformSettings: _*)
> > +    .dependsOn(IterateesProject, FunctionalProject, DataCommonsProject)
>
> Why is the json API depending on the Iteratee module?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/playframework/Play20/pull/754/files#r3114414>.
>
>