[
https://issues.apache.org/jira/browse/MNG-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484571#comment-16484571
]
Seckin Onur SELAMET commented on MNG-6415:
------------------------------------------
I kindly disagree with that statement. Java classloader cares about the order
of the entries listed in classpath. So the other applications/tools those are
built on top of it or those are helping java community to be more productive
must follow the same approach.
That statement can be an advice for a developer to avoid this kind of bugs or
some design rules violated by artifact providers but it is not a technical rule
Java features.
> 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)
