HTML Export creating new objects all the time

[Pino]

So, every time I export a model to HTML, even if I simply changed a note and nothing else, in GIT I end up with thousands of changes (which I can leave with) and a bunch of new objects and others that are deleted. This causes the website to grow exponentially unless I first delete all its content and then replace it with the new export, so it's a cumbersome waste of time that I hardly can justify.

Don't we have UUID for each object in the metamodel? How comes that they are not used to create unique objects when exporting the HTML?

Am I missing something here or there is a very big issue with the HTML exporter?

[Geert Bellekens]

Before exporting to HTML you should delete everything or you end up with a bunch of not used files.

The HTML generation is not "stable" the filenames can't be relied on to represent the same thing next time.

There seems to be little use to version control the HTML export as you can't compare two versions to each other in any usable way.

Geert

[Pino]

Before exporting to HTML you should delete everything or you end up with a bunch of not used files.

The HTML generation is not "stable" the filenames can't be relied on to represent the same thing next time.

There seems to be little use to version control the HTML export as you can't compare two versions to each other in any usable way.

Geert

Well, I suppose this is a big bug  I must use a version control because it is part of the CI/CD automation to publish the architecture website. This is a really bad one.

[Geert Bellekens]

I don't think it's a bug. It definitely looks like a deliberate design decision.

But of course it might not work as you were expecting.

Feel free to send a feature request to Sparx https://www.sparxsystems.com/support/forms/feature_request.html

Geert

[wivel]

Dont get your hopes up when it comes to changes to the HTML generator.

Nothing has happened there since EA version 7, and nothing will, AFAIK. I asked Sparx recently if we could expect the HTML generator to support the multiple languages now implemented in EA, and the answer was no. Sparx is focusing on WebEA and and Prolaberate for 'webification' and only keeps the HTML generator working with no additional functionality.

Henrik

[qwerty]

Dont get your hopes up when it comes to changes to the HTML generator.

Nothing has happened there since EA version 7, and nothing will, AFAIK. I asked Sparx recently if we could expect the HTML generator to support the multiple languages now implemented in EA, and the answer was no. Sparx is focusing on WebEA and and Prolaberate for 'webification' and only keeps the HTML generator working with no additional functionality.

Henrik

emphasis by me. "Laber" in German means "dumb talking". Now, was that Freudian?

q.