[
https://issues.apache.org/jira/browse/MNG-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910442#comment-17910442
]
Guillaume Nodet commented on MNG-8494:
--------------------------------------
The {{maven-compat}} is required at runtime when building sites for example.
Maven itself does not use it.
I once had a goal to remove {{maven-compat}} completely, but that's not on my
radar anymore.
Here again, I think switching plugins to the new API will solve the problem
automatically, so not sure it's worth pursuing. I'd rather switch them directly
to the new Maven API. Maven 5 should drop Maven 3 compatibility and all
{{/compat/maven-*}} artifacts imho. Maven 4 currently keeps some level of
compatibility with Maven 3 and Maven 2...
> Restore Maven 3 compatibility
> -----------------------------
>
> Key: MNG-8494
> URL: https://issues.apache.org/jira/browse/MNG-8494
> Project: Maven
> Issue Type: Task
> Components: API
> Reporter: Guillaume Nodet
> Priority: Critical
> Fix For: 4.0.0-rc-3
>
>
> The Maven 3 modules have been moved into the {{/compat/}} directory.
> But before this happened and the new Maven 4 API was introduced, those
> classes undergo quite some incompatible changes. Given they are now
> deprecated, it would make sense to restore them to full Maven 3.9.x
> compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
