Thanks for the response. I will check it out the suggested library.
I have decided to use the gson library, because its flexibility (the service
response might change over time, and extra/missing fields can be ignored
without any problem) and performance issues encountered at response
de-serializat
On 23.06.2014 08:25, jBeata wrote:
I'm referring to the "gson" JSON parsing library, that is used by the mapdust
plugin. This plugin uses gson version 1.5, the other plugin (not jet public)
uses gson version 2.2.4.
I could move to a new plugin the gson parsin library, and then update both
plugins
I'm referring to the "gson" JSON parsing library, that is used by the mapdust
plugin. This plugin uses gson version 1.5, the other plugin (not jet public)
uses gson version 2.2.4.
I could move to a new plugin the gson parsin libr
On 21.06.2014 15:24, Beata Jancso wrote:
Hi,
Perhaps to create another new plugin that gives access for both
plugins to the additional library?
Exactly. See [1], field 'Plugin-Requires'. E.g. ImportImagePlugin and
opendata plugin both depend on the geotools plugin.
If you need more guidance
Hi,
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 ne
___
josm-dev mailing list
josm-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/josm-dev
Hi,
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 ne
Hi,
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 ne
Hi,
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 ne
