maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6415) Project Artifacts Cache does not retain the order of classpath entries.
Date Tue, 22 May 2018 21:08:00 GMT

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

Michael Osipov commented on MNG-6415:
-------------------------------------

Java makes not guarantees in which order JARs are loaded, especially when you are using wildcard
classpaths. Never rely on the order. If you rely on, you seriously have a linkage error in
your application.

> Project Artifacts Cache does not retain the order of classpath entries.
> -----------------------------------------------------------------------
>
>                 Key: MNG-6415
>                 URL: https://issues.apache.org/jira/browse/MNG-6415
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.2
>         Environment: Windows 7, JDK8u144
>            Reporter: Seckin Onur SELAMET
>            Priority: Major
>              Labels: CLASSPATH
>         Attachments: [MNG-6415]_Fixes_Project_Artifact_Cache_classpath_order_retaining_issue_.patch
>
>
> Project artifacts cache does not retain the order of classpath entries.
> Wrong Object type used in implementation. HashSet can not guarantee the order of elements.
> In runtime ProjectArtifacts passed as LinkedHashSet already which is safe.
>  
> Possible fix is provided in comments section.



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

Mime
View raw message