title: Maven Assembly includes filtering
body: <p>Given the following dependency inclusion an a Maven assembly XML...</p>
  
  <pre><code>&lt;dependencySet&gt;
    &lt;includes&gt;
      &lt;include&gt;com.company.product:library:jar:*:*&lt;/include&gt;
    &lt;/includes&gt;
  </code></pre>
  
  <p>... why does the above filter fail to include library:jar that doesn't have a classifier?</p>
  
  <pre><code>[INFO] Reading assembly descriptor: assembly/release.xml
  [WARNING] The following patterns were never triggered in this artifact inclusion filter:
  o  'com.company.product:library:jar:*:*'
  </code></pre>
  
  <p>The reason for the additional wildcards in my pattern is that I also have a profile that builds all my libraries with the classifier "qa".  When I activate that profile, everything works, but under the default profile (which builds libraries with no classifiers) it fails.  </p>
  
  <p>If I change the filter to:</p>
  
  <pre><code>&lt;include&gt;com.company.product:library*&lt;/include&gt;
  </code></pre>
  
  <p>Then the maven build actually fails, with this error:</p>
  
  <pre><code>[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-
  plugin:2.3:single (make-assembly) on project java-package: Failed to create 
  assembly: Error adding file 'com.company.product:library:jar:1.0.0-SNAPSHOT' 
  to archive: C:\Subversion\JavaProj\library\target\classes isn't a file. -&gt; [Help 1]
  </code></pre>
  
  <p>Can someone suggest a pattern that will include jars either with or without a classifier?</p>