Updating depencies and fixing NPE for annotation processing #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
We are using this library in our API to serialize Java Objects, however due to old libraries and CVEs on the old libraries it triggers a lot of security warnings.
I have updated the Versions for the Libraries including:
moving to commons4
moving to latest version of reflections
set the log4j and log4j adapter as test scope dependencies, now library only uses latest version of slf4j 1.7.x.
I also ordered fields accessed by reflection by their name name to provide reproducable serialization of entities.
Add Null Checks to prevent NPE.
Updated version from 2.1.1-SN to 2.2.0
That would be nice if you can accept / review changes.