Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Environment:n/a
-
Number of attachments :
Description
Should we upgrade the used JAXB implementation (com.sun.xml.bind:jaxb-xjc) to the latest 2.2 version?
Any impact, or is it fully backwards compatible?
One benefit would be that in 2.2.5+ there is build-in support for configuring the output char encoding.
I configured the plugin as shown bellow. And it works fine with JAXB 2.2. Now the APT Deprecation warnings are gone, too