gnodet commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2205390080
> > > > > > I did investigate again and now I understand what actually happens: When I run current reporting plugins wich do _not_ depend on Maven Compat I still get CNFE, e.g., RepositorySystem or others because in [967d8fc](https://github.com/apache/maven/commit/967d8fc19cbb8a78410ceed70bd91c2e628da813) a bunch of classes were moved to Compat and are now gone. What apparantly was fine with Maven 3.x is now not possible with Maven 4. If all changes in [967d8fc](https://github.com/apache/maven/commit/967d8fc19cbb8a78410ceed70bd91c2e628da813) are correct then those plugins aren't compatible with 4 and need a separate branch for 4. > > > > > > > > > > > > > > > Do you know which class is required and not found ? > > > > > > > > > > > > Oh, sorry `RepositorySystem`. For those plugins, a dependency on maven-compat needs to be added afaik. > > > > > > > > > This means that compat cannot be removed for those plugins? How to proceed in case? > > > > > > All of these plugins are one Maven 3.6.3 already. I prefer the Resolver approach. Second option. > > Agreed, I think m-site-p is ok, it's maven-project-info-reports-plugin which depends on maven-compat and needs to be updated. Actually, adding maven-compat does not work, and switching to `org.apache.maven.bridge.MavenRepositorySystem` does not work too. The reason is the classes are present in maven-core 3.x and maven-compat 4.x. A real switch to maven-resolver api will work better. -- 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
