maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gili (JIRA)" <>
Subject [jira] [Commented] (MCOMPILER-317) Plugin generates wrong modulepath (dependencies listed in wrong order)
Date Wed, 20 Dec 2017 12:40:00 GMT


Gili commented on MCOMPILER-317:

[~rfscholte] It looks like the bug is in maven-project. See the comment I just posted:

> Plugin generates wrong modulepath (dependencies listed in wrong order)
> ----------------------------------------------------------------------
>                 Key: MCOMPILER-317
>                 URL:
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.7.0
>         Environment: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T03:58:13-04:00)
> Maven home: C:\Program Files\apache-maven-3.5.2\bin\..
> Java version: 9.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9.0.1
> Default locale: en_CA, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>            Reporter: Gili
> Testcase:
> If a project contains dependencies with the same module name (which is valid according
to then maven-compile-plugin invokes {{javac}}
with a modulepath containing dependencies in an (apparently) arbitrary order. If I place the
project in one directory, I get one order. If I place the project in another directory, I
get another order. This is 100% reproducible across multiple runs, across different computers.
> I suspect that somewhere deep inside the code someone is using {{HashMap}} which is leading
to undefined iteration order depending on the path being used.
> Expected behavior: dependencies should be listed in the same order as declared in pom.xml
> Actual behavior: regardless of whether I list {{ExtensionPresent}} before or after {{MyLibrary}},
the wrong order gets passed to {{javac}}.

This message was sent by Atlassian JIRA

View raw message