anchor.diff:  
   ++++
   <sample id="addExtraPlaySourcesets" dir="play/sourcesets" title="Adding extra source sets to a Play application">
  -                <sourcefile file="build.gradle" snippet="play-extra-sourcesets"/>
  -            </sample>
  +    <sourcefile file="build.gradle" snippet="play-extra-sourcesets"/>
  +</sample>
   ++++
   
   
  
positive.code: 
  ++++
  <sample id="configureRoutesCompiler" dir="play/play-2.4" title="Configuring routes style">
                  <sourcefile file="build.gradle" snippet="play-injected-routes-compiler"/>
              </sample>
  ++++
  
  
  
negative.code: </sample>
  ++++
  
  [NOTE]
  ====
  Play 2.6 has a more modular architecture and, because of that, you may need to add some dependencies manually. For example, https://playframework.com/documentation/2.6.x/Migration26#Guice-DI-support-moved-to-separate-module[Guice support was moved to a separated module]. Considering the following definition for a Play 2.6 project:
  
  ++++
  <sample id="play26Project" dir="play/play-2.6" title="A Play 2.6 project">
      <sourcefile file="build.gradle" snippet="play-platform-2.6"/>
  </sample>
  ++++
  
  You can add Guice dependency like:
  
  ++++
  <sample id="play26ProjectDependencies" dir="play/play-2.6" title="Adding Guice dependency in Play 2.6 project">
      <sourcefile file="build.gradle" snippet="play-dependencies-2.6"/>
  </sample>
  ++++
  
  Of course, pay attention to keep Play version and Scala version for the dependency consistent with the platform versions.
  ====
  
  
  [[configuring_play_sourcesets]]
  ==== Configuring the default source sets
  