rmannibucau commented on PR #11639: URL: https://github.com/apache/maven/pull/11639#issuecomment-3807979132
> Optional, provided and tests dependencies are not in <build>, so those ones are not impacted by the removal of <build>. the point is more that we can't drop useful information cause it is not used for a single use case without a proper replacement, think OSGi requirement (~provided scope for ex). > Javadoc and annotation dependencies are no longer in <build> with the new model. They are ordinary dependencies with a specific <type>. Therefore, they would not be impacted by the removal of <build> neither. Yes but to complete your PR idea you must remove them from `<dependencies>` too cause the consumer pom doesn't need them at all and more generally any dependency which is not a jar/zip of runtime scope should be removed - war overlay case included. > But this information is not in <build> neither, so it would be a separated discussion not impacted by the removal of <build>. Well my point was that removing build is an issue we hit so we can't do it now more than before since we dont have a fix for it plus the fact ultimately cleaning up dependencies will be challenging too with the new type workaround. -- 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]
