Use custom serialization for fileobject subclasses. #5211
Merged
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.
When LSP client issues project metadata command to inspect project structure / produced artifacts, the ArtifactSpec may containa reference to a FileObject, if the artifact was built already. The original idea was to serialize FileObjects as paths, but I made a wrong test -- the check should accept all FileObject subclasses.
In this case a MultiFileObject was serialized from Maven ArtifactSpec resulting in a serialization error:
since GSON serializer traversed deep into the FileObject.