Beirtí Ó'Nunáin created MSHARED-466:
---------------------------------------
Summary: Filtering dependencies does not retain the order of the
unfiltered list
Key: MSHARED-466
URL: https://issues.apache.org/jira/browse/MSHARED-466
Project: Maven Shared Components
Issue Type: Bug
Affects Versions: maven-common-artifact-filters-1.4
Reporter: Beirtí Ó'Nunáin
If you use the dependency:build-classpath mojo, you get the dependency list as
specified in the pom. However, if you introduce filtering, you end up losing
the dependency order. It seems that the
org.apache.maven.shared.artifact.filter.collection.ArtifactsFilter declares
'Set' instead of 'SortedSet' and that the
org.apache.maven.shared.artifact.filter.collection.AbstractArtifactFeatureFilter
returns a HashSet instead of a LinkedHashSet, even though a LinkedHashSet is
being passed in.
The impact of this is that you cannot generate a correctly-ordered classpath
when using filters. The fix is very straightforward, simply change the
filterIncludes and filterExcludes methods of AbstractArtifactFeatureFilter to
use a LinkedHashSet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
