Stephen Russett

>Mostly assertions extracted to a separate methods (for reusability) or assertions done inside a closure. There verifyAll cannot be used - only the first assertion is used (with the assert...

@leonard84 @szpak thinking about this more, I see the bigger question of: How can soft assertions be reused through something like traits.

@leonard84 any alternatives come to mind?

My use case is around Hazelcast usage: I have my primary ObjectMapper that is used for regular JSON with HTTP requests, etc. But i also have the SmileMapper for serialization...

@cowtowncoder the `with(...)` looks like a good solution. The with() would not be called continually? It should be similar to a app wide instance? With a reader and writer pre-configured...

@cowtowncoder after some further investigation into the use case, I have found that `with()` is good in principal but ultimately fails due to module reuse: The higher level scenario here...

This is also a problem for optional sub second precision. Where the trailing zeros are cut off. This seems to be a issue with the deeper dateTimeFormatter. The issue is...

It's not that the dates are "different". It's about knowing what the actual/original precision the date was collected at. You can have dates from many sensors from many different people...

@Flomix how are you producing your second example? `2019-04-29T16:04:12.000100Z" (Instant)` The issue as i understand it, and have had to write a wrapping class around Instant is: something like (1)2019-04-29T16:04:12.100000000Z...

@cowtowncoder Thanks for the followup. IMO, based on going through a impl and needing to retain trailing zeros and the precision in general (basically having sub-seconds in timestamps be optional...