[
https://issues.apache.org/jira/browse/MPMD-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722643#comment-17722643
]
Henning Schmiedehausen commented on MPMD-368:
---------------------------------------------
The build tool throwing warnings fails CI builds in a lot of organizations (it
does so in mine and in previous places that I worked). It may not fail at the
actual tool level but the CI harness detects warnings and fails the build.
Upgrading the tools in the tool chain is independent from the actual code.
Often the code developers don't even have control over the build pipeline or
the tools that are used. Having a build suddenly throw warnings that are
completely unrelated to the code itself but because of the combination of build
tool and build plugins without any actionable advice *and* doing so in a patch
level change is problematic from my PoV.
> Parameter 'localRepository' is deprecated
> -----------------------------------------
>
> Key: MPMD-368
> URL: https://issues.apache.org/jira/browse/MPMD-368
> Project: Maven PMD Plugin
> Issue Type: Bug
> Affects Versions: 3.20.0, 3.21.0
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> Probably since Maven 3.9.1 this warning is seen in builds:
> [WARNING] Parameter 'localRepository' is deprecated core expression; Avoid
> use of ArtifactRepository type. If you need access to local repository,
> switch to '${repositorySystemSession}' expression and get LRM from it instead.
> This broke the CI and has been worked around (MPMD-367) but the root cause
> should be addressed. This same issue might appear in other plugins as well
> and break their CIs that check to see there are no warnings in a build.
> I'm not sure whether this can be fixed without breaking compatibility with
> older Maven versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
