title: Maven dependency aliasing
body: <p>I've just noted that my war contains both <code>woodstox-core-asl-4.4.1.jar</code> and <code>woodstox-core-5.0.2.jar</code>.  They are two different version of the same library, but the library changed both groupId and artifactId.  Furthermore both are included in my war as transitive dependencies by two different modules of my project.</p>
  
  <p>I know that I can use <code>exclusions</code> to remove the old version of the library but in this case I should also explicitly "include" the new version in case that module would be used alone (that is not with the other one that includes <code>woodstox-core-5.0.2.jar</code>).</p>
  
  <p>I don't like this solution.  Is there any way to declare that <code>woodstox-core</code> is an alias of <code>woodstox-core-asl</code> so that Maven includes only one of these jars?</p>
  
  <p>A similar problem affects old Spring 2.x that published both an all-in-one artifact and smaller separated artifacts.  However I think that the most common issue is the one related to artifacts that change their groupId and/or artifactId.</p>