maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MNG-6650) Java11 Regression Bug: Transitive dependencies not resolved
Date Fri, 03 May 2019 17:00:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832662#comment-16832662
] 

Jörg Hohwiller commented on MNG-6650:
-------------------------------------

As you can already see by PR [https://github.com/devonfw/devon4j/pull/84] the following commit
acts as workaround for this bug:

[https://github.com/devonfw/devon4j/pull/84/commits/518b7f0afdb36fdc79a83048fb688347d5c835d7]

I already invested some time to isolate a minimal project but this more tricky than expected.
Just having a 2 modules project with one module having these dependencies with jdk profile
activation and another one depending on the first and having a class importing CsrfToken does
not reproduce the bug.

> Java11 Regression Bug: Transitive dependencies not resolved
> -----------------------------------------------------------
>
>                 Key: MNG-6650
>                 URL: https://issues.apache.org/jira/browse/MNG-6650
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.6.0
>         Environment: Works with Java 1.8
> Fails with Java 11
> Reproduced on Mac and Windows as well as in travis-ci (linux).
>            Reporter: Jörg Hohwiller
>            Priority: Major
>
> I have found a strange situation where maven seems to be unable to resolve transitive
dependencies for a particular dependency but only in Java11+
> The failing build can be found here with all the analysis:
> [https://github.com/devonfw/devon4j/pull/82]
> As you can read there with all the details the error is related to a profile with
> <activation>
>    <jdk>[9,)</jdk>
>  </activation>
> That should fire on Java11 and seems to do but as a result all dependencies are eliminated
in this case what seems like a strange maven bug.
> The Code to reproduce the issue locally can also be cloned from here:
> [https://github.com/hohwille/devon4j/tree/feature/16-java-11]
> (be sure to checkout this "feature/16-java-11" branch)
> After building you can even reduce and reproduce the error from {{templates/server/target/test-classes/projects/basic/project/basic}}
> Just "cd" there and run "mvn clean install" with Java1.8 and with Java11.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message