title: SBT Compiler Plugin as Transitive Dependency
body: <p>I have a library that uses the macro paradise plugin (referred to as macro-provider library). In the <code>build.sbt</code>,</p>
  
  <pre><code>addCompilerPlugin("org.scalamacros" % "paradise" % "2.0.0" cross CrossVersion.full)
  </code></pre>
  
  <p>to gain access to the <strong>macro annotations</strong>. </p>
  
  <p>When adding the macro library as a <code>libraryDependency</code> to a separate project (referred to as macro-consumer project), the annotations are present, but the macro implementation is never called. Adding the macro paradise compiler plugin to the macro-consumer project <code>libraryDependencies</code> solves the problem.</p>
  
  <p><em>Is it possible to include compiler plugins as transitive dependencies? This would free consumers of the macro library from adding the required plugin.</em></p>
  
  <hr>
  
  <p><strong>Update #1:</strong></p>
  
  <p><em>The <code>addCompilerPlugin</code> helper adds the dependency to the <code>libraryDependencies</code> and sets the dependency with a <code>configuration = Some("plugin-&gt;default(compile)")</code> within the macro-provider library.</em></p>
  
  <p><em>Adding the <code>paradise</code> dependency in the <code>libraryDependencies</code> of the macro-provider library causes the  artifact to show up in the macro-consumer project. It does not add the dependency as a compiler plugin.</em></p>
  
  <p><strong>Update #2:</strong></p>
  
  <p><em>Setting <code>autoCompilerPlugins := true</code> in the macro-consumer project in conjunction with <strong>Update #1</strong> does not resolve the issue.</em></p>