laeubi commented on issue #11089: URL: https://github.com/apache/maven/issues/11089#issuecomment-3402214296
> Not exactly. The warning shown in the console is about an API that will not work at all in Maven 4 To what I should care when running solely on maven 3? > at least as it stands today. Today I run on Maven 3 and don't care about Maven 4 at all > The deprecation is for making developer aware that they should not specify the sources with only a path, as there is other information worth providing. The Javadoc already said what developers should use. [Not in Maven 3.9.11](https://github.com/apache/maven/blob/d47bdcc9212d9dfafe9448405290ad2d4bd4c699/maven-core/src/main/java/org/apache/maven/project/MavenProject.java#L355-L357) and I even have no way to call the non deprecated method now so I must again adapt if I ever want to migrate to maven 4.... > A risk of this approach is that plugins sometime use Maven in unexpected ways, so maybe some plugins would be broken if the list was no longer an instance of ArrayList. The message complains about using an iterator what is independent from the impls, but this sounds much more useful: 1. In Maven 3 do like you proposed and do NOT warn! 2. In Maven 4 warn if the approach is still used -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
