Support wildcard exclusions in Pom parser

[hamnis]

Maven 3.2 supports a new way of excluding everything.

See the attached project for more information.

This means that you may find newer published artifacts which allows exclusions on a more general level.

Sbt does not find the dependencies which have this.

[mkurz]

Can this get a higher priority?
IMHO this issue is a bug - not an "enhancement".

We just ran into the limitation of sbt not supporting wildcard exclusions when using Hibernate 5.2.1:
https://hibernate.atlassian.net/browse/HHH-10916
Hibernate has a dependency on dom4j which excludes all transitive dependencies:

    <dependency>
      <groupId>dom4j</groupId>
      <artifactId>dom4j</artifactId>
      <version>1.6.1</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>

The problem is that now even dom4j itself isn't resolved by sbt and we end up having a ClassNotFoundException - because of the missing dom4j jar.

[mkurz]

Infos:
https://maven.apache.org/docs/3.2.1/release-notes.html#Transitive_dependency_excludes_MNG-2315
https://issues.apache.org/jira/browse/MNG-2315

[eed3si9n]

@mkurz Thanks for clearing that up.

[mkurz]

@eed3si9n Thanks! Hopefully this get fixed soon...

[mkurz]

Is there a chance this will make it in the next sbt version?
Could someone please assign the milestone?

[eed3si9n]

I would say this is something we can push till the next sbt 1.0.x milestone, unless there's a support case from a Lightbend customer or we can get the community to contribute the fix.

[dwijnand]

Fixed in #2731.

[mkurz]

@dwijnand Thank you for fixing this!

[dwijnand]

Damn I should've been more explicit in the PR description.

All credit must go to @jtgrabowski for fixing this.

[mkurz]

OK so thank you @jtgrabowski for fixing this! 👍 😄