On 5 December 2015 at 09:49, Alan Bateman <alan.bate...@oracle.com> wrote:
>
> On 04/12/2015 19:10, Peter Levart wrote:
>>
>> :
>>
>> You would have to invoke jodaBeansModule.addRead(guavaModule); from your
>> org.joda.beans code before 1st use of any guava type. In Addition, you would
>> have to ensure guava is part of runtime configuration - either implicitly by
>> some module in your configuration requiring guava or explicitly by adding
>> "-addmodule guava" to the java launcher command line.
>
> Yes, that's right, there is enough to support all the scenarios. The
> use-guava-if-it-happens-to-be-there scenario is somewhat awkward though as
> it would means using -addmods. On the other hand, the
> use-guava-if-someone-hands-me-a-guava-type scenario is straight-forward, it
> just means reading the module at run-time (easy).
>
> -Alan
