[
https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606811#comment-17606811
]
Naveen Kasthuri commented on MPMD-335:
--------------------------------------
[~michael-o] I think this is a valid ticket. Custom repositories do not work
for me either. If I downgrade to v3.13.0 - it works. With no other changes
except an upgrade to v3.19.0, I receive the DependencyResolutionException.
> PMD 3.15.0 and 3.16.0 do not use project repository
> ---------------------------------------------------
>
> Key: MPMD-335
> URL: https://issues.apache.org/jira/browse/MPMD-335
> Project: Maven PMD Plugin
> Issue Type: Bug
> Reporter: Andre Kalamandeen
> Priority: Major
>
> I've tried to upgrade PMD to 3.16.0 and noticed that when building it tries
> to get artifacts from the default maven repository instead of the repository
> configured in the project.
> This causes issues with the build as certain artifacts are only available in
> the custom repository.
>
> The build error:
> {code:java}
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.16.0:pmd
> failed: org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException: The following
> artifacts could not be resolved: [REMOVED]: Failure to find [REMOVED] in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
