Oxygen XML Forum

Hello,
I have some DITA content that I am publishing to HTML Responsive Webhelp via OxygenXML

For each export, OxygenXML appends the date-time to each import, as a buildId: The date-time is unique for each publishing run, and can make it appear to our Version Control System that the content has changed - though it hasn't actually.

DITA_OT does not specify the buildId when exporting to HTML - so if none of the content has changed, it's not a new version. Can the buildId be excluded from HTML imports during the OxygenXML to HTML publishing process?

I got this great answer from Radu a couple of years ago, when I faced the same problem:
https://stackoverflow.com/a/76848786/92441

Hello,
The build ID is generated to ensure that the browser loads any updates to the template or resources that may occur between deployments.
If you no longer want the build ID to be generated, the approach recommended by my colleague is a valid solution.

Hello,
The build ID is generated to ensure that the browser loads any updates to the template or resources that may occur between deployments.
If you no longer want the build ID to be generated, the approach recommended by my colleague is a valid solution.

Thanks for your answer. I got it.