You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/02/25 11:29:14 UTC

[GitHub] [maven-plugin-tools] slawekjaranowski commented on a change in pull request #74: [MPLUGIN-395] Upgrade Maven Reporting API/Impl to 3.1.0

slawekjaranowski commented on a change in pull request #74:
URL: https://github.com/apache/maven-plugin-tools/pull/74#discussion_r814693581



##########
File path: maven-plugin-plugin/pom.xml
##########
@@ -350,7 +350,8 @@
               <settingsFile>src/it/settings.xml</settingsFile>
               <streamLogsOnFailures>true</streamLogsOnFailures>
               <filterProperties>
-                <sitePluginVersion>3.3</sitePluginVersion>
+                <sitePluginVersion>3.11.0</sitePluginVersion>
+                <projectInfoReportsPlugin>3.2.2</projectInfoReportsPlugin>

Review comment:
       Why not use the same version like in project?
   Do we want later use another version in tests then in project?
   I afraid that next we update version in project but not for tests.
   And how to managed version if we have plugin version from parent?




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org