Jacek Lach

Currently test-with-junit only writes output to the junit .xml reports. This pull makes it output both the xml reports and the human readable output of `mvn clojure:test`, to the report...

@cowtowncoder I believe you meant to tag @jcustenborder

Workaround: break git, so that the 'native' git describer fails instaed of producing wrong output: ``` $ git rebase --exec 'GIT_DIR=/tmp/.git ./gradlew printVersion' develop (.. happy gradlew output) ```

Similar issue in #186

:+1: - while I agree that just bumping the limit is probably best, it seems people are wary to do this globally in case things break. Having a opt-in flag...

an empty optional is surely within the domain of `any`. It seems reasonably that it might not serialize as a 204 and instead as `null` or whatever else - as...

FYI we had to go back to conjure-jersey over this as it proved to be a bigger break than we thought

Isn't it always up to the code calling a conjure client to know what the exact type of an `any` endpoint is (presumably based on the query they sent) and...

Specifically I can generate these reports on exactly the same transaction history, only by changing what is the `trade_asset_type` and `crypto_list` in my configuration:   

Yeah, but I did not realise that could cause the CGT calculation to be off by so much. The warning certainly doesn't suggest urgency. And when running with `--debug`, it's...