zacthompson commented on issue #996: URL: https://github.com/apache/maven-dependency-plugin/issues/996#issuecomment-3787658698
One could argue that dependency analysis has different implications for "application"-level maven modules (I think of them as leaf nodes in the dependency tree), compared to analyzing shared libraries. In particular, the "used but undeclared" case is of lesser concern for an application: as long as the dependency is present, that same dependency version will get shipped with the product, no matter its position in the tree. So perhaps one can set `ignoredUsedUndeclaredDependencies` to e.g., "org.springframework.boot" for such modules. I think the simplest workaround for people encountering this issue is probably to do the above, and then also add your chosen starters to `usedDependencies`. Of course, this would block the plugin from being able to warn you if your list of dependencies is excessive, but you are forced to accept some of that limitation by choosing to use the starters in the first place. -- 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]
