michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2203130039
> > > > > 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. Deleting no, but we cannot also replace the code to Resolver with 3.6.3 baseline? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
