title: Is there a Maven "compiler-only" scope for dependency artifacts
body: <p>I realise this is more of a semantic quest rather than a functionality quest.</p>
  
  <p>I have three types of compile-scope dependencies:</p>
  
  <ol>
  <li><p>Compile-only scope, not used at run-time.
  GWT client-side dev, MVP4G, RestyGWT, Source retention annotation processors. I use REST, so I don't need GWT server side.</p></li>
  <li><p>Provided - Hibernate jars required for compilation but provided by JBoss.</p></li>
  <li><p>Compile + runtime jars.</p></li>
  </ol>
  
  <p>For case 2, we could use provided scope. Case 3, we would use compile scope.</p>
  
  <p>However for case 1, I use provided scope, even though JBoss does not provide those files at all. Nor are they needed at run-time.</p>
  
  <p>Anyway, don't you think Maven should provide for a synonym for "provided" for a scope where the artefacts are not really needed except at compile time? Perhaps, should there be a "compile-only" scope?</p>