[MWRAPPER-143] - The wrapperVersion property is not used in only-script mode#145
[MWRAPPER-143] - The wrapperVersion property is not used in only-script mode#145slawekjaranowski merged 2 commits intomasterfrom
Conversation
|
Resolve #291 |
1 similar comment
|
Resolve #291 |
The sh_type_only-script integration test was expecting the wrapperVersion property to be present in only-script mode, but PR apache#145 removed this property from only-script mode since it's not used. Updated the test to match the expected behavior.
… mode The only-script mode doesn't use the wrapper distribution, this property is now only added to the maven-wrapper.properties file when other types are used.
2e049d2 to
2c69885
Compare
|
Original issue that added version: So, the intent of the version in the properties file was in fact to ease various automations to detect, and maybe suggest an upgrade for wrapper itself. We are now breaking automations for the second time... Hence, this PR is wrong. And sorry for being late to the party. |
|
I'm in the same boat as @cstamas - only discovered this change when Renovate created an upgrade PR for Maven Wrapper to version 3.3.3 which removes the |
|
For update automation tools need a reliable way to determine the current version of Maven Wrapper. The I saw that Renovate plans to determine the Maven Wrapper version based on a regex check on the scripts themselves (renovatebot/renovate#37779), which should be more reliable than reading Could Maven Wrapper provide its version in a more robust (machine-readable) way? |
|
@breun please comments in open linked issue |
Ok, comment reposted here: #364 (comment) |
…nly-script mode (apache#145)" This reverts commit 91bdb45.
* Revert "[MWRAPPER-143] - The wrapperVersion property is not used in only-script mode (#145)" This reverts commit 91bdb45. * Revert #145, but leave wrapperUrl assertions
|
|
Solve |
The only-script mode doesn't use the wrapper distribution, this property is now only added to the maven-wrapper.properties file when other types are used.
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MWRAPPER-XXX] - Fixes bug in ApproximateQuantiles,where you replace
MWRAPPER-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.
Fixes #291