JOSM plugin development - How to avoid duplicate additional library


I was wondering how to handle situations when a custom plugin uses an additional library that is already used by some another plugin? Let’s say that plugin A uses library L version 1, and plugin B uses the same library L but version 2.
The JOSM plugin development guide says that a plugin needs to contain all the additional libraries that uses. What would be the optimal solution for these type of situations? Perhaps to create another new plugin that gives access for both plugins to the additional library?

Thanks in advance!

I would recommend to ask such a special question to the JOSM-dev Mailing list, if not done already …