[
https://issues.apache.org/jira/browse/MWRAPPER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462589#comment-17462589
]
Jeremy Norris commented on MWRAPPER-42:
---------------------------------------
I think that in order to utilize timestamp comparisons, you would need to use
`wget --no-use-server-timestamps` so that wget doesn't set the mtime of
maven-wrapper.jar equal to that of the webserver's mtime.
On a separate note: I also noticed that it appears when the mvnw script falls
back to using MavenWrapperDownloader, it will use an existing copy of
MavenWrapperDownloader.class that may have originated from compiling with an
older version of MavenWrapperDownloader.java instead of the current release
version that is checked into the repository.
> 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)
