Project HTML report

[Rafael Walter]

Hi,

      How do I generate an HTML report for the whole project (all root packages) in EA 6.5?

      (I can to generate reports for a specific package using Shift+F8, and thats ALMOST what I need...)

Thanks,

Rafael Walter

[«Midnight»]

Hi Rafael,

I don't have EA 6.5 up, so I really cannot say. In EA 7.1 you can generate the report normally. Make sure the root package is selected in the Project Browser tree, right-click the root, and choose the HTML Report from the context menu.

If that does not work in 6.5 there is something you might try as a workaround. Extract the entire model to XMI, from the root package. Then create a new, empty project, and create an empty package under the root node. Try importing the model you extracted, but import it into the empty package rather than the root node. You might also want to clear the Strip GUIDs option so that any reported GUIDs will be the same as your 'real' model.

Once you've done the import you should be able to create an HTML report from your 'dummy' root package.

David

[Oliver F.]

Hi,

      How do I generate an HTML report for the whole project (all root packages) in EA 6.5?

If you are refering to several root models in your project then I am afraid this does not work.
You can not do cross model report generation.
You can of course have a documentation model root which holds all diagrams with links to elements from other models.
However when generating the report from this model EA does not generate details for elements in different model roots (well, not even in different packages, if you start below their hierarchy).

Oliver

[Martin Terreni]

This is certainly a problem I hope sparx fix.

[Oliver F.]

This is certainly a problem I hope sparx fix.

From Sparx point of view I can understand this.
The starting point for a report generation is a package hierarchy (or a root model) so having several root models (especially from a conceptual point of view) means having several hierarchies and in most cases there was a reason for modelling it that way.

Cross model or cross package references fall into a similar category.
Documenting an object in another hierarchy level, what does that mean ? Documenting all sub elements below and references from that element to other elements ?
That will very quickly lead to a recursive issue with the known problems of recursion- like circle dependencies, conflicts, etc.

So I do not consider this being a bug nor a feature. It is simply not here so whoever would like to have it (with all consequences) will have to request that as a feature at Sparx.

Oliver