[
https://issues.apache.org/jira/browse/MWRAPPER-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837829#comment-17837829
]
ASF GitHub Bot commented on MWRAPPER-128:
-----------------------------------------
cstamas commented on code in PR #126:
URL: https://github.com/apache/maven-wrapper/pull/126#discussion_r1567790763
##########
maven-wrapper-plugin/pom.xml:
##########
@@ -34,7 +34,7 @@ under the License.
<description>The Maven Wrapper Plugin is a plugin that provides support for
the Maven Wrapper by unpacking Maven Wrapper Distribution to the current
project.</description>
<prerequisites>
- <maven>${mavenVersion}</maven>
+ <maven>3.2.5</maven>
Review Comment:
Yeah, but _all plugin builds_ use at least two Maven version: 3.9.6 and ...
usually 3.6.3. So what "issue in runtime" you expect? Okay, if test coverage is
poor... but then we fix and improve coverage, and life goes on...
> Remove legacy
> -------------
>
> Key: MWRAPPER-128
> URL: https://issues.apache.org/jira/browse/MWRAPPER-128
> Project: Maven Wrapper
> Issue Type: Task
> Components: Maven Wrapper Plugin
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.3.0
>
>
> This plugin still uses legacy stuff: zap it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
