[DROOLS-1170] drools-pmml: use 'xjc' binary instead of jaxb2-maven-pl… #814
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.
…ugin
idea was to create new profile which would be jdk9-specific
and use the exec-maven-plugin only there. However, this does not
work because the classes generated directly by 'xjc' and the
plugin are not exactly the same. The one big difference is that
the plugin useis 'is' prefix for Boolean properties whereas
xjc will use 'get' prefix (e.g. public Boolean isAdult() vs
public Boolean getAdult()). It seems the later is correct as
'is' should only be used for primitive boolean, and not for object
type Boolean (http://download.oracle.com/otndocs/jcp/7224-javabeans-1.01-fr-spec-oth-JSpec/).
To make the configuration easier, the plugin was removed
and the jxc is called directly.
The only thing I am wondering about is if it save to assume the
xjc
binary is on PATH? This may not always be the case. Maybe we should use ${env.JAVA_HOME}/bin/xjc instead?@mariofusco, @ge0ffrey could you please take a look and let me know what you think?