anchor.diff:  
   Using the project name for filtering is one option. Using <<writing_build_scripts.adoc#sec:extra_properties,extra project properties>> is another.
   
  -=== Example: Adding custom behaviour to some projects (filtered by project properties)
  -
  -.Project layout
  +.Adding custom behaviour to some projects (filtered by project properties)
  +====
  +[.multi-language-sample]
  +=====
  +.Project layout
  +[source, groovy]
   ----
   .
   ├── bluewhale
  
positive.code: │               └── web.xml
  └── settings.gradle
  ----
  
  NOTE: The code for this example can be found at **`samples/userguide/multiproject/dependencies/webDist`** in the ‘-all’ distribution of Gradle.
  
  
negative.code: 
  As we have seen, you can run a multi-project build by entering any subproject dir and execute the build from there. All matching task names of the project hierarchy starting with the current dir are executed. But Gradle also offers to execute tasks by their absolute path (see also <<#sec:project_and_task_paths,Project and task paths>>):
  
  .Running tasks by their absolute path
  ----
  > gradle -q :hello :krill:hello hello
  include::{samplesPath}/userguide/multiproject/tropicalWithProperties/water/multiprojectAbsoluteTaskPaths.out[]
  ----
  
  