You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/04/23 10:24:00 UTC
[jira] [Closed] (MPMD-335) PMD 3.15.0 and 3.16.0 do not use project repository
[ https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MPMD-335.
-------------------------------
Resolution: Not A Problem
This is zero related to this plugin. Go to the users mailing list.
> 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.7#820007)