maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] [Commented] (MNG-6500) Dependency resolution broken with Java 11
Date Tue, 06 Nov 2018 18:52:00 GMT


Jörg Hohwiller commented on MNG-6500:

Where on earth does that come from?

Not from our POM: []


Do I need to do a special setup to build the project?




Does this build has any special profiles etc?


Nope. It has some special profiles but nothing is needed by default.

So is there anything inside maven triggering this dependency that is not available in JDK
11 anymore?

Or do we have some strage (transitive) dependency that is triggering this dependency via a
jdk version activated profile?

> Dependency resolution broken with Java 11
> -----------------------------------------
>                 Key: MNG-6500
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.4
>         Environment: Java 11
>            Reporter: Jörg Hohwiller
>            Priority: Major
> I am facing an issue that some transitive dependencies are missing on maven dependency
resolution. This reproducible works fine with older Java (java8) and always fails with java
> The code that fails can be found in this feature branch:
> []
> A detailed description of the issue can be found here:
> []
> It would be awesome if someone could have a look and make maven work smooth with Java

This message was sent by Atlassian JIRA

View raw message