Closed yunkaiOr2 closed 4 years ago
You have to implement an alternative ObjectMapper and add it to the configuration in order to use a different JSON implementation, I'll look into being able to exclude it although some things (like .asJson) is it's own implementation that leverages GSON and cannot be replaced. So excluding gson will break that
I've made the default object mapper lazy in 3.8.06, but you will still need gson on the path in order to work with the asJson methods as they do not use any other implementation
i want to remove dependency get a minimum library
when i exclude gson replace my custom json lib(like jackson, fastjson....) i get err
java.lang.NoClassDefFoundError: com/google/gson/Gson
now the library default and Strong binding gson
feature:
public interface ObjectMapper {