Missing Files when Generating MDG EA 14.1

[philchudley]

Hi All

Has anyone else experienced the following when generating an MDG in EA 14.1?

1) Create an MDG consisting of the usual profile, custom diagram(s) and toolbox(es)
2) Use the SPECIALIZE Publish -> Publish Diagram as UML Profile for the custom diagram(s), and toolbox(es) to create the XML files
3) Use the SPECIALIZE Publish -> Publish Package as UML Profile for the profile to create the XML files
4) Generate the MDG and select to include Profile, Diagrams, Toolboxes (etc) in the MTS

Only the Package Profile XML shows up the profile selections for profiles / diagrams / toolboxes! That is the XML files generated for the diagram(s) and toolbox(es) are not listed within the MDG Builder dialogs.

If I revert to EA 13.5 and re-generate all the XML files, the MDG builds fine in EA 14.1

Any thoughts?

Phil

[Geert Bellekens]

Hi Phil,

I've use the 14.1 MDG generation without any problems on several different occasions and situations.
Not sure why it's not working for you.

Geert

[qwerty]

I'd guess it's a sleepy eye syndrome. I can't count how often I accidentally stored profile files in the wrong place (until I got myself up and replaced that silly MTS with an own script that actually looks into the files to verify that they contain what they should). Have a coffee break and try from the start.

q.

[Sunshine]

Just like Geert I've used v14.1 to generate an MDG without problems. Well thats if you don't count spending ages
trying finding out where they'd moved the generate diagram profile command.
The symptom of only getting the package profiles sounds like something to do with config of the MDG generation in the MTS file. Have you got two MTS files by any chance and V13 is pointing to one and V14.1 pointing to another?
I once created two MTS files by accident due to burning the midnight oil and that caused me a similar problem. Thats the only thought I have at the moment.

[qwerty]

I have no MTS at all. All that MDG generation is about is to cat a couple of XML files in a bigger one. EA does that without looking. My mini-script just croaks if one of the concatenated source does not contain what it should. Simple and effective. Never had any real issues since dropping that MTS.

And believe me: I've been in the same situation as you more than once.

q.

[KP]

Hi All

Has anyone else experienced the following when generating an MDG in EA 14.1?

1) Create an MDG consisting of the usual profile, custom diagram(s) and toolbox(es)
2) Use the SPECIALIZE Publish -> Publish Diagram as UML Profile for the custom diagram(s), and toolbox(es) to create the XML files
3) Use the SPECIALIZE Publish -> Publish Package as UML Profile for the profile to create the XML files
4) Generate the MDG and select to include Profile, Diagrams, Toolboxes (etc) in the MTS

Only the Package Profile XML shows up the profile selections for profiles / diagrams / toolboxes! That is the XML files generated for the diagram(s) and toolbox(es) are not listed within the MDG Builder dialogs.

If I revert to EA 13.5 and re-generate all the XML files, the MDG builds fine in EA 14.1

Any thoughts?

Phil

Please check that you gave your profile a non-blank version number and notes field when saving. The technology wizard checks each .xml file is a "valid" profile before listing it, and believes (rightly or wrongly) that a valid profile must have non-blank values in these fields. There is a bug fix in the works.

[Paolo F Cantoni]

[SNIP]
Please check that you gave your profile a non-blank version number and notes field when saving. The technology wizard checks each .xml file is a "valid" profile before listing it and believes (rightly or wrongly) that a valid profile must have non-blank values in these fields. There is a bug fix in the works.

Yes, Phil,

It took us a good couple of hours to figure THAT one out! 

Also, @KP, since a bug fix is on its way, can we infer that The technology wizard "wrongly" requires the non-blank version number?   

Paolo

[philchudley]

Hi All

Many thanks for all the replies, the addition of the version number to replace the blank version number in the diagram and toolbox profiles solved the issue.

All the best

Phil