(1230) Silent Failure to load MDG

[Paolo F Cantoni]

When I installed build 1230, my MDG failed to load.  There was NO error message , just no ticked MDG - although it was on the list.

It turned out that the reason was that although we are developing a new MDG, we haven't yet been able to remove the ArchiMate2:: definitions.  We get around this by renaming/removing  the ArchiMate MDG in the MDGTechnologies sub-folder so that they don't interfere with ours.  We normally do that after our smoke tests for the new version.

My bug is not that the MDG didn't load but that there wasn't an error message as to why.
In previous versions, there were some anomalous behaviour if both MDGs were loaded, but at least they loaded.

Now there's some extra checks and as a consequence the second MDG (with the same internal ID) is NOT loaded.  There should be a message to that effect - not just a silent fail.

Over time, we will be replacing the ArchiMate2 content with our own.

Reported,
Paolo

[Geert Bellekens]

I think there actually is a record in the System Output saying something like "duplicate MDG ID", but if you don't have that pane visible you'll miss it of course.

Geert

[Paolo F Cantoni]

I think there actually is a record in the System Output saying something like "duplicate MDG ID", but if you don't have that pane visible you'll miss it of course.

Geert

Just checked... Nothing in the System Output.

In any event, if the error is reported there, there IS an API call to make the window visible!  As a matter of course, any such initialisation errors should be made visible!

Paolo

[qwerty]

I moaned about EA's silence when it comes to any kind (!) of add-in failures since a long time. No expectations...

q.

[Paolo F Cantoni]

I moaned about EA's silence when it comes to any kind (!) of add-in failures since a long time. No expectations...

q.

I know you did, but the dripping tap eventually makes a hole in the granite...

Paolo

[Glassboy]

I know you did, but the dripping tap eventually makes a hole in the granite...

I'm going for Sir Les Patterson for that one (although I feel the axiom is probably more true for sedimentary rocks than igneous rock, unless there is also ice involved).

[Uffe]

I think there actually is a record in the System Output saying something like "duplicate MDG ID", but if you don't have that pane visible you'll miss it of course.

Geert

Not sure about a duplicate MDG Technology warning. On 11.1 at least, what happens if you add the paths to your development and deployment areas at the same time, both versions of the MDG Technology will show up but you will only be able to select one at a time.

There is an error message "WARNING: Duplicate profile name: <profile>, detected in technology ID: <technology>", which you get if you include the same profile in two different MDG Technologies, and EA does open System Output to show you that message.

/Uffe

[Paolo F Cantoni]

I know you did, but the dripping tap eventually makes a hole in the granite...

I'm going for Sir Les Patterson for that one (although I feel the axiom is probably more true for sedimentary rocks than igneous rock, unless there is also ice involved).

Well!

Thank you for the compliment, but it's actually a Paolo original. 

Paolo

[Paolo F Cantoni]

[SNIP]
Not sure about a duplicate MDG Technology warning. On 11.1 at least, what happens if you add the paths to your development and deployment areas at the same time, both versions of the MDG Technology will show up but you will only be able to select one at a time.

There is an error message "WARNING: Duplicate profile name: <profile>, detected in technology ID: <technology>", which you get if you include the same profile in two different MDG Technologies, and EA does open System Output to show you that message.

/Uffe

Not in build 1230.  It's been accepted as a bug (and reported by another user) so maybe it's a regression failure.

Paolo