You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current 2.0.0 version has in the OSGi manifest mandatory imports for the different JSON providers:
com.fasterxml.jackson.core;version="[2.4,3)",
com.fasterxml.jackson.databind;version="[2.4,3)",
com.fasterxml.jackson.databind.type;version= "[2.4,3)",
com.google.gson;version="[2.3,3)",
com.google.gson.internal; version="[2.3,3)",
com.google.gson.reflect;version="[2.3,3)",
net.minidev.json;version="[2.1,3)",
net.minidev.json.parser;version="[2.1,3)",
net.minidev.json.writer;version="[2.1,3)"
It would be great to make all these dependencies optional, so that the OSGi bundle gets resolved without all the JSON providers. Of course you have to provide at least one provider to be able to run jasonpath successfully. However, this solution would be much leaner.
Beside the changes in the manifest file, also changes in the DefaultsImpl must be made. This class must be made more flexible: If the json-smart provider is not in the classpath, this class could look for providers which are in the classpath and use the first found provider.
If you which I can create a pull request.
The text was updated successfully, but these errors were encountered:
I found out that changes in DefaultsImpl are not necessary. You just have to set an other Default instance in the configuration before the first call is made.
The current 2.0.0 version has in the OSGi manifest mandatory imports for the different JSON providers:
com.fasterxml.jackson.core;version="[2.4,3)",
com.fasterxml.jackson.databind;version="[2.4,3)",
com.fasterxml.jackson.databind.type;version= "[2.4,3)",
com.google.gson;version="[2.3,3)",
com.google.gson.internal; version="[2.3,3)",
com.google.gson.reflect;version="[2.3,3)",
net.minidev.json;version="[2.1,3)",
net.minidev.json.parser;version="[2.1,3)",
net.minidev.json.writer;version="[2.1,3)"
It would be great to make all these dependencies optional, so that the OSGi bundle gets resolved without all the JSON providers. Of course you have to provide at least one provider to be able to run jasonpath successfully. However, this solution would be much leaner.
Beside the changes in the manifest file, also changes in the DefaultsImpl must be made. This class must be made more flexible: If the json-smart provider is not in the classpath, this class could look for providers which are in the classpath and use the first found provider.
If you which I can create a pull request.
The text was updated successfully, but these errors were encountered: