dashorst opened a new issue, #1862: URL: https://github.com/apache/wicket/issues/1862
Audit the dependencies declared by Wicket's modules and determine which ones Wicket does not need. Every dependency a published module declares with `compile` scope ends up on the classpath of every application using that module. Over time some of these may have become unused, belong in `test` scope, could be `optional`, or are pulled in only for a feature that could live elsewhere. Scope of the audit: - For each published module (`wicket-util`, `wicket-request`, `wicket-core`, `wicket-extensions`, `wicket-ioc`, `wicket-spring`, `wicket-cdi`, `wicket-guice`, `wicket-velocity`, `wicket-auth-roles`, `wicket-jmx`, `wicket-devutils`, `wicket-bean-validation`, `wicket-native-websocket`, `wicket-tester`, `wicket-extensions-tester`, `wicket-migration`, experimental modules), list the resolved dependencies with their effective scope. - Flag dependencies that are declared but unused, used but undeclared (only arriving transitively), in the wrong scope (test libraries on the compile classpath), or candidates for `optional`. - List the release date of each dependency's version in use and of its latest release, to spot libraries that are abandoned or far behind. - Propose concrete changes per module, noting which ones affect applications (a transitive dependency disappearing is a behaviour change for users who relied on it). -- 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]
