[
https://issues.apache.org/jira/browse/MRESOLVER-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-414.
-------------------------------------
Assignee: Tamas Cservenak
Resolution: Fixed
> MRESOLVER-377 makes several metadata related Maven IT fail
> ----------------------------------------------------------
>
> Key: MRESOLVER-414
> URL: https://issues.apache.org/jira/browse/MRESOLVER-414
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Change MRESOLVER-377 most probably altered how Maven {{-U}} and other CLI
> options (and possibly settings) is applied, and now is not applied to
> metadata.
> Failed (and possibly related) ITs:
> * MavenITmng4554PluginPrefixMappingUpdateTest.testitRefetched
> * MavenITmng4433ForceParentSnapshotUpdateTest.testit
> * MavenITmng5064SuppressSnapshotUpdatesTest.testit
> * MavenITmng4745PluginVersionUpdateTest.testitForceUpdate
> * MavenITmng4679SnapshotUpdateInPluginTest.testit
> * MavenITmng4554PluginPrefixMappingUpdateTest.testitForcedUpdate
> * MavenITmng4482ForcePluginSnapshotUpdateTest.testit
> * MavenITmng4361ForceDependencySnapshotUpdateTest.testit
> * MavenITmng4326LocalSnapshotSuppressesRemoteCheckTest.testit
> Problem: the original change was kinda half-baked. Proper solution: Resolver
> internally should fully split artifact and metadata policies, while it should
> leave on "surface" (session iface and default imple) getter/setter for apps
> that does not want to distinguish between the two (whether as they are
> legacy, or intentionally).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
