[ 
https://issues.apache.org/jira/browse/MWRAPPER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813072#comment-17813072
 ] 

ASF GitHub Bot commented on MWRAPPER-123:
-----------------------------------------

bmarwell opened a new pull request, #117:
URL: https://github.com/apache/maven-wrapper/pull/117

   Old behaviour was to always use h * 331 + 104 (because on most shells, 
`printf %d "'%str"` always evaluated to 104).
   
   For now, use this constant as this does not change behavour.
   
   It might be feasible to do another kind of string-to-int conversion in 
another PR to implement the intended behaviour.
   
   ---
   
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [X] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MWRAPPER) filed 
          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.
    - [X] Each commit in the pull request should have a meaningful subject line 
and body.
    - [X] Format the pull request title like `[MWRAPPER-123] - Fixes bug in 
ApproximateQuantiles`,
          where you replace `MWRAPPER-XXX` with the appropriate JIRA issue. 
Best practice
          is to use the JIRA issue title in the pull request title and in the 
first line of the 
          commit message.
    - [X] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [X] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
          be performed on your pull request automatically.
    - [X] You have run the integration tests successfully (`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](https://www.apache.org/licenses/icla.pdf) 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](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [X] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [X] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   




> only-mvnw fails on AIX' ksh implementation
> ------------------------------------------
>
>                 Key: MWRAPPER-123
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-123
>             Project: Maven Wrapper
>          Issue Type: Bug
>    Affects Versions: 3.1.1
>            Reporter: Benjamin Marwell
>            Priority: Urgent
>
> the script {{only-mvnw}} contains this snippet in a line to calculate a hash:
> {code:bash}
> printf %d "'$str"
> {code}
> The idea is to convert {{$str}} to a number, where {{'}} has a special 
> meaning for {{%d}} conversion. However, there are two problems with it:
> 1. It does not work on ksh on AIX (because this conversion is not posix 
> compliant), so the script will not run on AIX.
> 2. It will only use the first letter, which is alway {{h}} (from the string 
> always being a valid URI).
> For now, replace it with the ASCII constant 104 (ASCII value of h). The 
> intended behaviour can be restored in another PR if feasible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to