[
https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862526#comment-17862526
]
ASF GitHub Bot commented on MNG-7266:
-------------------------------------
michael-o commented on PR #1487:
URL: https://github.com/apache/maven/pull/1487#issuecomment-2203132098
> > > > > > These two:
> > > > > >
> > > > > > * maven-plugin-tools/maven-plugin-plugin
> > > > > > * maven-project-info-reports-plugin
> > > > >
> > > > >
> > > > > maven-plugin-tools/maven-plugin-plugin does NOT depend on
maven-compat, does it? Also, it contains traces of archaic (Maven2 times) when
pom was considered "metadata" and plugin had to maintain maven-metadata.xml as
well (something not needed since Resolver 1.9.x, as all data deployed generally
are "artifacts", no more "metadata" to be handled by client code needed).
Unsure what to be done here, maybe just bite the bullet, and raise the m-p-p
prerequisite to 3.9.x (this would raise _build time_ Maven requirement for all
built plugins, but not runtime requirements) and drop all this cruft.
> > > > > Am looking into the other one.
> > > > > EDIT: the other one still uses MAT.... so convert it to resolver?
... and shared dep tree that is also to be dropped/deprecated. so a LOT of
deprecated stuff...
> > > >
> > > >
> > > > We could also switch them directly to the Maven 4 API...
> > >
> > >
> > > I'd prefer to solve this for 3.x as well to make easier for us.
> >
> >
> > We won't be able to get rid of maven-compat in Maven 3.x branch.
>
> Also fwiw, m-plugin-p does not depend on maven-compat or MAT anymore (and
still supports Maven 3 plugins for now).
But that is on m-plugin-tools on master, no? The 3.x branch will remain
as-is in this regard?
> 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)
