Closed mestebangutierrez closed 6 years ago
You will need to upgrade the version of jaxb2-basics-runtime
everywhere. So far there is one known issue with this: #74. This will be fixed but right now this does not allow you to use old generated code and new generated code (0.11.1+) together. I am sorry about this, I was trying to make it a drop-in replacement but made a mistake there. When #74 is fixed you should be able to use old code and new code with the new runtime simultaneously. Strategies in the new runtime work with both old interfaces like CopyTo
as well as new interfaces like CopyTo2
.
Let me fix #74, then we'll see if there are other issues.
@mestebangutierrez I'm closing this as there was no reaction from you.
I'm currently using v0.9.4 together with -seems to be- legacy Fluent API plugin, Value Constructor plugin Commons Lang plugin, Default Value plugin, and Namespace-prefix plugin. My current POM looks like this:
When trying to change the
jaxb2-basics.version
to0.11.1
I start seeing compiler problems with the generated code when the module is used in other modules, i.e.,cannot access org.jvnet.jaxb2_commons.lang.CopyTo2
,cannot access org.jvnet.jaxb2_commons.lang.Equal2
,cannot access org.jvnet.jaxb2_commons.lang.HashCode2
,cannot access org.jvnet.jaxb2_commons.lang.ToString2
.Are there any caveats regarding the migration from such and old version to a new one and the support to legacy plugins?