timtebeek commented on PR #1917: URL: https://github.com/apache/maven/pull/1917#issuecomment-2481541215
Hmm; you're right. I only just now noticed _all_ of the classes here are in `compat`, as opposed to just the few I'd reverted when tests broke on the changed backwards compatibility. Guess that means there's little sense in changing this now; luckily the changes were mostly automated. Thanks for pointing it out! I did already have my eye on completely removing `maven-compat` and was considering automation in that area next. Is there any set of steps on what would be required? Would this better fit a Slack or mailling list conversation? -- 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
