[
https://issues.apache.org/jira/browse/MNG-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487809#comment-16487809
]
Robert Scholte commented on MNG-6415:
-------------------------------------
{quote}We have never documented this to be retained throughout.{quote}
Maybe not explicit, but surely implicit. The result of a build is consistent
which is possible because the order of jars stays the same. It is a known
practice that if you have classpath-order issues, you can put that dependency
more up in your pom.
Anyway, this is how dependency resolution worked for years, we're now hit by an
unintended change which can easily be fixed. Better to change the documentation
than to disappoint the projects that relied on this "bug/feature".
> 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)
