[
https://issues.apache.org/jira/browse/MPMD-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810168#comment-16810168
]
Andreas Dangel commented on MPMD-278:
-------------------------------------
I think, that problem is the one mentioned at MPMD-277.
Do you use the aggregate=true parameter?
This will make pmd execute on the reactor root before all the modules are
compiled, which is problematic. The bug MPMD-277 will be fixed, to not try to
load the modules artifacts from the repository in that case. But if the modules
are not compiled before, PMD's results might not be accurate (e.g. it could
find more false positives).
> pmd-plugin 3.11.0 fails in multi module release builds
> ------------------------------------------------------
>
> Key: MPMD-278
> URL: https://issues.apache.org/jira/browse/MPMD-278
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
> Affects Versions: 3.11.0
> Reporter: Andreas Müller
> Priority: Major
>
> When using maven-pmd-plugin 3.11.0 the pmd plugin fails in release builds of
> multi module maven projects:
> {noformat}[INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd (pmd) on project xxx:
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd
> failed:
> org.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException:
> Could not find artifact xxx:jar:<Version that will be released> in <remote
> maven repository> -> [Help 1]
> {noformat}
> or
> {noformat}[INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd (pmd) on project xxx:
> Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd
> failed:
> rg.apache.maven.reporting.MavenReportException:
> org.eclipse.aether.resolution.DependencyResolutionException:
> Failure to find xxx:jar:<Version that will be released> in <remote maven
> repository> was cached in the local repository,
> resolution will not be reattempted until the update interval of <remote repo>
> has elapsed or updates are forced -> [Help 1]{noformat}
> Normal build are working fine.
> I guess the problem is that the plugin is looking for the released version in
> the remote repository before it's actually transferred after the successful
> release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
