[
https://issues.apache.org/jira/browse/MPMD-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779457#comment-16779457
]
Andreas Müller commented on MPMD-278:
-------------------------------------
Actually I don't know why we changed the phase from {{verify}} to {{test}}.
But also when not overriding the phase, the error still occurs.
Here is the log sequence. I hope this helps:
{noformat}[INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ xxx ---
[INFO] Executing goals 'clean verify'...
...
[INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ xxx ---
[INFO] [INFO] >>> maven-pmd-plugin:3.10.0:check (pmd-checks) > :pmd @ xxx >>>
[INFO] [INFO]
[INFO] [INFO] --- maven-pmd-plugin:3.10.0:pmd (pmd) @ xxx ---
>>>>>>>> With maven-pmd-plugin 3.11.0 the build fails right here, with 3.10.0
>>>>>>>> it goes on like this:
[INFO] [INFO]
[INFO] [INFO] <<< maven-pmd-plugin:3.10.0:check (pmd-checks) < :pmd @ xxx <<<
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-pmd-plugin:3.10.0:check (pmd-checks) @ xxx ---
...{noformat}
----
{quote}The exception doesn't really fix to the the configured goals{quote}
To me the documentation on the site you mentioned is a bit misleading, as the
{{check}} / {{cpd-check}} goals are invoking {{pmd}} / {{cpd}}.
The documentation is more clear on the "goal" sites, e.g.
https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html
-> "Invokes the execution of this plugin's goal pmd prior to executing itself."
We're using it like mentioned on the official pmd website:
https://pmd.github.io/pmd/pmd_userdocs_tools_maven.html#integrated-into-the-build-process.
> 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)
