Wow! I had no idea code generation was used in this project. Not knowing anything about the code base, here are some random thoughts.

If manual edits have been made on classes created by code generation, then I would really avoid replacing those classes by their newly re-generated versions. I think the approach you are adopting (running code generation independently for ODF 1.2 and 1.3 and spotting the differences) is good: those changes then need to be backported manually to the code base.

In any case this sounds like a really significant project which should really not be a prerequisite for releasing what you have already.

from odftoolkit.

Basics of Code Generation Update

Currently, the Code generation can only be triggered by the following Java test
generator/schema2template/src/test/java/schema2template/example/odf/OdfGenerationTest.java
Only the generation of ODF 1.2 is enabled - the generation of ODF 1.0, 1.1 and 1.3 is being temporarily disabled (at the bottom of the test class).

The generated output - the ODF dom and pkg Java sources - can be found within:
generator/schema2template/target/generated-sources/java/odf1.2

The Apache velocity templates, which are being used to generate the ODFDOM Java sources, are from now only with the related (ODFDOM) project:
odfdom/src/codegen/resources

from odftoolkit.