[
https://issues.apache.org/jira/browse/MNG-8687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944457#comment-17944457
]
Tamas Cservenak edited comment on MNG-8687 at 4/14/25 8:34 PM:
---------------------------------------------------------------
Sadly, this is not simple, the effort put into this would be huge. Moreover,
the old patches are not applicable, as they were made against "drifted" source
(and not against original classes, those restored by MNG-8494). So I am punting
on this: Maven4 "compat" modules are not JIMFS capable fully (Resolver demos do
work, but for example MIMA MMR extension – full access to model reader does
not).
was (Author: cstamas):
Sadly, this is not simple, the effort put into this would be huge. Moreover,
the old patches are not applicable, as they were made against "drifted" source
(those restored by MNG-8494). So I am punting on this: Maven4 "compat" modules
are not JIMFS capable fully (Resolver demos do work, but for example MIMA MMR
extension – full access to model reader does not).
> Restore compat classes ability to work on JIMFS
> -----------------------------------------------
>
> Key: MNG-8687
> URL: https://issues.apache.org/jira/browse/MNG-8687
> Project: Maven
> Issue Type: Task
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> The Resolver 2 can, but accompanying (Maven compat) classes lost this ability
> due work in MNG-8494. IMO we need to restore this capability, but we need to
> be very careful to not break binary compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
