Currently, the Generator validates "decode" and "encode" identifiers in all bindings to make sure they:
Resolve.
Provide compatible arguments and return types.
This works for those identifiers that are resolvable to the jsonx-maven-plugin during the execution of the build, but this may not be the case in all situations. There may be situations where the identifier is defined in the same project for which the jsonx-maven-plugin is first supposed to run (which most always happens before the compile phase). This means that such classes would not be compiled yet to be resolved.
Instead of failing the invocation of the jsonx-maven-plugin, it should instead throw a warning, and continue the build.
Currently, the
Generator
validates "decode" and "encode" identifiers in all bindings to make sure they:This works for those identifiers that are resolvable to the
jsonx-maven-plugin
during the execution of the build, but this may not be the case in all situations. There may be situations where the identifier is defined in the same project for which thejsonx-maven-plugin
is first supposed to run (which most always happens before thecompile
phase). This means that such classes would not be compiled yet to be resolved.Instead of failing the invocation of the
jsonx-maven-plugin
, it should instead throw a warning, and continue the build.