Werner Keil comments

Results 431 comments of


                                            Werner Keil

Money.toString() and Money.parse(…) not symmetric anymore

There are two parts to this problem: 1. Using `MonetaryAmount amount = Monetary.getDefaultRounding().apply(this);` in all relevant `toString()` operations, not just `Money`, which in the given example already rounds down the...

Money.toString() and Money.parse(…) not symmetric anymore

Actually the majority of test failures were pretty much the same, so avoiding the round-down plus an adjustment of the scale that also takes the `maxScale and `fixedScale `combination into...

Money.toString() and Money.parse(…) not symmetric anymore

Did not hear anything by either one, so I assume that is resolved.

Money.toString() and Money.parse(…) not symmetric anymore

The hardcoded scale for toString() was what had to be fixed here, so adding it back would only be possible as an optional property, Please create an enhancement request here,...

Money.toString() and Money.parse(…) not symmetric anymore

@stefanzilske I saw #364 had been around for some time, we did not really plan to do this (especially the desire to just print "a" or something) until a much...

IMF Rate Providers can be very slow to update

Neither the timeouts nor the UserAgent or headers look like they're working anymore in a console/Maven build.

IMF Rate Providers can be very slow to update

- [x] Use curl instead of wget in the shell script for now - [x] Different structure of the default file to overcome JPMS loading problem - [x] Try to...

IMF Rate Providers can be very slow to update

Based on above checklist, let's look into a [comparison of Java HTTP clients](https://reflectoring.io/comparison-of-java-http-clients/). The inner workings of `IMFRemoteSearchCallable` have to be updated to use something other than `URLConnection` which works...

IMF Rate Providers can be very slow to update

Fixed with #400

IMF Rate Providers can be very slow to update

@brassier This was fixed with 1.4.3 The actual problem was accessing the IMF and other exchange rates using the old JDK `URLConnection`. This was fixed by using Okhttp3. Where passing...