desruisseaux commented on PR #1744: URL: https://github.com/apache/maven/pull/1744#issuecomment-2372305329
> We really need to reverse things: have maven-api-impl implement all these, and let "legacy" (like compat was in mvn3) rely on new API, instead the other way around... It is fine for me. The problem is just that I don't really know what is new API and what is legacy API. If `MavenProject` is legacy API, I didn't realized that. If this is the case, maybe before any further work, we should start by putting an `@Deprecated` annotation on all legacy API, together with a link to new API? -- 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
