[
https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849654#comment-17849654
]
ASF GitHub Bot commented on MNG-7266:
-------------------------------------
michael-o commented on PR #1487:
URL: https://github.com/apache/maven/pull/1487#issuecomment-2132856197
> > > @cstamas @michael-o one blocker after upgrading to latest site is
[AbstractProjectInfoReport.java](https://github.com/apache/maven-project-info-reports-plugin/blob/master/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java)
which uses the `org.apache.maven.repository.RepositorySystem` class from
`maven-compat`. That part also uses MAT...
> >
> >
> > This is something I need to look at as a whole (reporting plugins) with
@cstamas when the current Maven Reporting votes are done and Maven Site Plugin
is done as well. I am currently working on lifting the reporting plugin to
3.6.3 first, whenever possible. So please bear with me.
>
> Sure, np. I just had a quick look again at this PR with the latest site
plugin, so just wanted to report the outcome.
Thanks, I did have this on my radar. I assumed that the cleanup in Maven
Reporting Impl was enough. It obviously wasn't.
> Remove maven-compat module
> --------------------------
>
> Key: MNG-7266
> URL: https://issues.apache.org/jira/browse/MNG-7266
> Project: Maven
> Issue Type: Sub-task
> Reporter: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Maven-core does not depend on maven-compat anymore (runtime or compile time).
> Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we
> want to drop it before 4.0.0 ?
> [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
