[
https://issues.apache.org/jira/browse/MENFORCER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved MENFORCER-331.
---------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
> Maven-enforcer-plugin's use of aether-util in transitive dependency
> -------------------------------------------------------------------
>
> Key: MENFORCER-331
> URL: https://issues.apache.org/jira/browse/MENFORCER-331
> Project: Maven Enforcer Plugin
> Issue Type: Dependency upgrade
> Components: Standard Rules
> Reporter: Tomo Suzuki
> Assignee: Enrico Olivelli
> Priority: Major
> Fix For: 3.0.0
>
> Original Estimate: 168h
> Time Spent: 10m
> Remaining Estimate: 167h 50m
>
> Hi Maven developers,
> (following "Contributing" section of
> [maven-enforcer-plugin|https://github.com/apache/maven-enforcer#contributing])
>
> I'm thinking to raise a PR to fix an issue below, so that
> maven-enforcer-plugin can work with maven-resolver-util without explicit
> "exclusion" element. Let me know what you think!
> While writing a custom enforcer rule, I encountered NoSuchMethodError
> org.eclipse.aether.util.ConfigUtils.getFloat. I believe it is caused by
> transitive dependency in org.eclipse.aether:aether-util. The class is also in
> org.apache.maven.resolver:maven-resolver-util:1.3.1. [A workaround with
> exclusion
> element|https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/master/enforcer-rules/pom.xml#L64]
> just worked fine for me but I'd like to contribute to fix the root cause if
> possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
