The published POM for json-path 2.10.0 declares only json-smart and slf4j-api, but the jar ships classes such as JacksonJsonProvider and GsonJsonProvider that reference jackson-databind and gson. Could these be declared as <optional>true</optional> dependencies so tooling that works from POM metadata can discover them?
The published POM for json-path 2.10.0 declares only json-smart and slf4j-api, but the jar ships classes such as
JacksonJsonProviderandGsonJsonProviderthat reference jackson-databind and gson. Could these be declared as<optional>true</optional>dependencies so tooling that works from POM metadata can discover them?