[
https://issues.apache.org/jira/browse/MWRAPPER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463036#comment-17463036
]
Herve Boutemy commented on MWRAPPER-42:
---------------------------------------
we'll need to start by creating an integration test to reproduce the issue: I
suppose that we can add it at plugin level to the existing ones that will do
run once with wrapper plugin 3.1.0 then with wrapper plugin LATEST to see if
the the update happened or not
then we'll work on fixing
are you interested to creating the IT, please?
on MavenWrapperDownloader.java:
1. I suppose the feedback is more theoretical, because this is used on *nix
only and only when curl and wget are not available: did you really reproduce?
2. this deserves another separate Jira issue...
> maven-wrapper fails to self-update maven-wrapper.jar
> ----------------------------------------------------
>
> Key: MWRAPPER-42
> URL: https://issues.apache.org/jira/browse/MWRAPPER-42
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
> Affects Versions: 3.1.0
> Reporter: Jeremy Norris
> Priority: Major
> Fix For: 3.1.1
>
>
> In cases where users do not check-in the maven-wrapper.jar into their
> repositories, after executing `mvn wrapper:wrapper -Dtype=script` to update,
> the newly updated `mvnw` script will continue to use an older version of
> `.mvn/wrapper/maven-wrapper.jar` that was previously downloaded.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
