title: What is the maven equivalent of implementation dependencies in gradle?
body: <p>I recently learned that <a href="https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_separation" rel="nofollow noreferrer">gradle has <code>api</code>/<code>implementation</code> "scopes" for dependencies</a>, and I was trying to figure out if there's a maven equivalent of the <code>implementation</code> in gradle. None of the maven dependency scopes seem exactly right for this - <code>provided</code> makes it not a runtime dependency, <code>compile</code>/<code>runtime</code> don't seem do the correct thing, ... and so it seems that there's not a direct equivalent. </p>
  
  <p>Basically, I have a dependency of my library that is required at compile-time (for my library)/runtime (for code that uses my library), but I don't want to be in the <em>compile</em> classpath of code that depends on my library. Is this possible to do with maven?</p>