[
https://issues.apache.org/jira/browse/MSHARED-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368161#comment-16368161
]
Robert Scholte commented on MSHARED-683:
----------------------------------------
This code should be compatible with both the {{org.sonatype}} and
{{org.eclipse}} packages. This is a typical library which must work for a wide
range of Maven versions, not just the latest.
Taken a closer look at the diff, there's one thing I can have a look at: the
changes for {{o.a.m.s.a.f.c.ArtifactTransitivityFilter.java}}
All others seems like a huge search and replaceAll, where all classes starting
with SonatypeAether start using org.eclipse.aether classes. And for the filters
the javadoc entries are suddenly duplicated due to this change.
bq. They depend on some scarily broken libraries, which is a problem for
distros like Debian.
Can you provide more details? I'm sure there's a better solution.
> Use maven-resolver instead of (eclipse-)aether
> ----------------------------------------------
>
> Key: MSHARED-683
> URL: https://issues.apache.org/jira/browse/MSHARED-683
> Project: Maven Shared Components
> Issue Type: Dependency upgrade
> Components: maven-common-artifact-filters
> Reporter: Chris West (Faux)
> Priority: Major
>
> PR: https://github.com/apache/maven-common-artifact-filters/pull/1
> Stop using the old `aether` and `eclipse-aether` libraries, who's code is now
> part of `maven-resolver`, under the `org.eclipse` package. The old libraries
> are very abandoned, to the point that their websites have gone missing. They
> depend on some scarily broken libraries, which is a problem for distros like
> Debian.
> Tests green. Only non-find-and-replace changes is to add some properties:
> * `<javaVersion>7` as `maven-resolver` uses 7 and otherwise enforcer gets
> angry, and
> * `<maven.version>3.5.2`, as pre-3.5 maven used aether for other reasons, so
> it still ends up polluting the tree.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
