[
https://issues.apache.org/jira/browse/MPIR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495745#comment-17495745
]
Hudson commented on MPIR-413:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP "new" »
maven-project-info-reports-plugin » master #3
See
https://ci-maven.apache.org/job/Maven/job/maven-github/job/maven-project-info-reports-plugin/job/master/3/
> Plugin repositories defined in project are not used by plugin-management
> report
> -------------------------------------------------------------------------------
>
> Key: MPIR-413
> URL: https://issues.apache.org/jira/browse/MPIR-413
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: plugin-management
> Affects Versions: 3.2.1
> Reporter: Piotr Zygielo
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 3.2.2
>
>
> Given: project that defines pluginRepository != central and manages plugin
> available from such repository
> When plugin-management report is requested
> Then
> # not user-friendly stack trace from exception is logged at INFO level
> {quote}[INFO] Generating "Plugin Management" report ---
> maven-project-info-reports-plugin:3.2.1:plugin-management[INFO] Could not
> build project for: groovy-eclipse-compiler:Error resolving project artifact:
> org.codehaus.groovy:groovy-eclipse-compiler:pom:3.7.1 was not found in
> https://repo.maven.apache.org/maven2 during a previous attempt. This failure
> was cached in the local repository and resolution is not reattempted until
> the update interval of central has elapsed or updates are forced for project
> org.codehaus.groovy:groovy-eclipse-compiler:pom:3.7.1
> +ST{quote}
> # the plugin in produced report is not linked to its site url
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
