[ https://issues.apache.org/jira/browse/MPMD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Dangel updated MPMD-335: -------------------------------- Summary: Aggregate mode doesn't use additional repositories (was: PMD 3.15.0 and 3.16.0 do not use project repository) > Aggregate mode doesn't use additional repositories > -------------------------------------------------- > > Key: MPMD-335 > URL: https://issues.apache.org/jira/browse/MPMD-335 > Project: Maven PMD Plugin > Issue Type: Bug > Components: PMD > Affects Versions: 3.15.0, 3.16.0, 3.17.0, 3.18.0, 3.19.0 > Reporter: Andre Kalamandeen > Assignee: Andreas Dangel > Priority: Major > Fix For: 3.20.0 > > Attachments: MPMD-335-aggregate-private-repo.zip > > > 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)