On 19-03-2021 21:28, Łukasz Dywicki wrote:
Hey Jurrie,
From context you shared it seems you have an complete maven build. In
fact it sounds to me like an embedded build with Yocto. ;-)
If you do maven build then it also means that you can use *any* of
available maven plugin to do post-processing of generated sources files.
Long time ago there was maven-code-replacer-plugin, there are also ant
tasks which you can use after sources are made.
By this way you will have consistent checksums and avoid troubles with
CXF modifications.
Hi Łukasz,
Thanks for your reply, and for thinking along. You're correct in that
it's a Maven build. I'm not in the embedded field, so I'm not using
Yocto :) I would like to have my build reproducible because of escrow
requirements.
I thought about using another plugin for post-processing. But after
giving it some thought, it feels wrong. I think you shouldn't use the
one plugin to fix something for another plugin. In the extreme case
where maven-code-replacer-plugin has a bug or omission, should I use yet
another plugin to fix that? :)
In fact, I already have the code for CXF and cxf-xjc-utils on a branch.
The code is in a state that's common for many of my branches: working,
but ugly :) I'd like to clean it up and submit it as pull requests to
the CXF project. But I would like to know what direction to do that
clean up, so the pull requests stand a chance of being accepted.
With kind regards,
Jurrie
