Hi,

Sorry for the confusion, but seems this was already done at some point, but not documented (other than a small mention of https://downloads.prosysopc.com/opcua/Prosys_OPC_UA_SDK_for_Java_4_Release_Notes.html#version-4-3-0).

In the configuration (maven or the standalone) do

And then it shouldn’t output the javadoc at for the type (that basically only included the timestamp).

Hmm good point, I think we have not that much checked them. I don’t think that is doable directly without us making a new release (and I cannot guarantee that it would be in the next one, but let’s see). We do currently use a lib called JavaPoet, so it depends does it have deterministic output, but I think at the moment the Codegen just has internally things in a Set etc. so the output might not be deterministic due to that.

However, maybe instead an alternative solution could be to run some sort of an auto-formatter externally after you have run the generator? For example: https://github.com/google/google-java-format. Though, as an idea maybe we could include something like that internally and just format the output regardless (maybe with a flag to control), but that is something to be investigated later. In general I would assume you to have something similar for non-generated code anyway (that formats them when you save the file), maybe you can just run that manually.

P.S.
One option also, depending how much you like is to have a separate part that generates the model, produces an artifact that is included to the real project as source code dependency (e.g. in maven dependency plugin to unpack and include it as extra sources via the build helper plugin). Though, you would need to exclude any files you wish to modify manually. Technically method implementations can also be plugged from the outside, so the only thing requiring manual modifications is if you wish to store some state in the XXXTypeNode(s).