cstamas commented on a change in pull request #66:
URL: https://github.com/apache/maven-plugin-tools/pull/66#discussion_r793342175
##########
File path: maven-plugin-plugin/pom.xml
##########
@@ -296,7 +276,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-plugin-plugin</artifactId>
- <version>3.6.0</version><!-- cannot use ${mavenPluginToolsVersion}
property because release plugin would try to update -->
Review comment:
Um, no idea, I tend to avoid m-release-p, never used it (aside of Maven
projects). But, if this (otherwise perfectly valid) construct "does not work"
with m-release-p, isn't the release plugin that needs to be fixed? Or we want
to sprinkle "workarounds" all around as "release plugin would try to update"?
--
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-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
