You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/04/24 08:10:00 UTC
[jira] [Commented] (MNG-7408) Explain reporting plugin version automatic selection (in Maven 3)
[ https://issues.apache.org/jira/browse/MNG-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527095#comment-17527095 ]
Hudson commented on MNG-7408:
-----------------------------
Build failed in Jenkins: Maven » Maven TLP » maven » MNG-7457 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7457/2/
> Explain reporting plugin version automatic selection (in Maven 3)
> -----------------------------------------------------------------
>
> Key: MNG-7408
> URL: https://issues.apache.org/jira/browse/MNG-7408
> Project: Maven
> Issue Type: Improvement
> Components: Sites & Reporting
> Affects Versions: 3.8.4
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.8.5, 4.0.0-alpha-1, 4.0.0
>
>
> reporting plugin version looks like normal version = you need to define a version for build stability https://maven.apache.org/ref/3.8.4/maven-model/maven.html#class_reporting
> in Maven 2, it did not even benefit from pluginManagement version selection
> but since Maven 3 MNG-4162, it benefits not only from pluginManagement version but also from plugin: we need to make that clear, because versions of report plugins are a pain for users who don't know about this, because it force them to define a property that will be used both in pluginManagement/plugin and reporting
> and since Maven Site Plugin 3.4, it also benefits from pluginManagement configuration
> see https://maven.apache.org/shared/maven-reporting-exec/
--
This message was sent by Atlassian Jira
(v8.20.7#820007)