You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/15 10:41:00 UTC
[jira] [Commented] (MSHARED-683) Use maven-resolver instead of
(eclipse-)aether / Require Java 7
[ https://issues.apache.org/jira/browse/MSHARED-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722099#comment-16722099 ]
Hudson commented on MSHARED-683:
--------------------------------
Build failed in Jenkins: Maven TLP » maven-common-artifact-filters » MSHARED-683 #2
See https://builds.apache.org/job/maven-box/job/maven-common-artifact-filters/job/MSHARED-683/2/
> Use maven-resolver instead of (eclipse-)aether / Require Java 7
> ---------------------------------------------------------------
>
> 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)