Bump maven-dependency-plugin from 3.1.2 to 3.3.0
Bumps maven-dependency-plugin from 3.1.2 to 3.3.0.
Commits
e52bc02[maven-release-plugin] prepare release maven-dependency-plugin-3.3.00ec0a52Fix Jenkins url77e42ca[MDEP-796] Upgrade Maven Parent to 3578976c0[MDEP-795] Update Jetty to 9.4.45.v20220203 (#202)a8d4690[MDEP-788] Upgrade maven-reporting-impl to version 3.1.025ca833(doc) Update link to Github PR docs76d59f0[MDEP-789] Improve documentation of analyze - Non-test scopedb66d2b2Bump mockito-core from 4.2.0 to 4.3.1b057234Bump slf4j-simple from 1.7.32 to 1.7.36f64d4f7[MDEP-787] allow ignoring non-test-scoped dependencies- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot rebase
@dependabot rebase
dependabot rebase
@dependabot rebase
do the warnings trigger the build failure?
do the warnings trigger the build failure?
@dizzzz yes, seems that the new version detects more unused stuff:
Warning: Unused declared dependencies found:
Warning: org.apache.logging.log4j:log4j-jul:jar:2.17.2:runtime
Warning: Non-test scoped test only dependencies found:
Warning: org.xmlunit:xmlunit-matchers:jar:2.9.0:compile
Warning: org.eclipse.jetty:jetty-http:jar:9.4.45.v20220203:compile
@adamretter I did some research in that problem and there are test related code (package org.exist.test) in the exist-core module that depends on testing libraries, that may needed to be separated out of the main source tree into some other location. As I'm not that experienced with Maven I do not know how to separate out something like test fixtures to be used within other modules as test dependencies though...
Superseded by #4631.