Alan Evans

Yeah, that sounds great.

How do you mean? like this: ``` curl rate.sx/btc.1Nh7uHdvY6fNwtQtM1G5EZAFPLC33B59rB 474.27659636 ``` For fiat value: ``` curl usd.rate.sx/btc.1Nh7uHdvY6fNwtQtM1G5EZAFPLC33B59rB 5,581,744.66 ``` Alternative chain: ``` curl rate.sx/bch.1Nh7uHdvY6fNwtQtM1G5EZAFPLC33B59rB 27.00474466 ``` For multiple chains, same...

I'd say accept one at first. If people want to see multiple, for the meantime they can just: ``` curl usd.rate.sx/btc.1Nh7uHdvY6fNwtQtM1G5EZAFPLC33B59rB+bch.1Nh7uHdvY6fNwtQtM1G5EZAFPLC33B59rB ```

@HDouss I cannot reproduce this from your example. You don't say what the failure is, but the test does not fail. https://github.com/westonized/jcabi-aspects/commit/34a21ffca23177e78b9de239bad90db072f111cf

@dmarkov blocked, waiting on OP to comment

@HDouss Ok, I see it in your branch, no idea what the difference is: ``` Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.51 sec

@HDouss I'm not sure we can deal with this, there is no javax method on the interface for specific validation on a static and hibernate explicitly states it does not...

@HDouss I just cherry picked your commit on to 0.22.2, it still fails there. So I don't believe your example demonstrates the same issue that stopped people wanting to upgrade.

@HDouss Ok, seen it on 0.21.1, 0.22 seems ok too. Definitely introduced in 0.22.1

@HDouss This looks like the prime commit candidate 3e2b3456113d932829e71841200a0be607ee4a47 "Replace our makeshift JSR-303 validation implementation with hibernate's" from PR #169/issue #34 As soon as that happened, we entered hibernate's house...