Looks like the problem is that something is spelled in the Australian way.
If you put 'realisation' in the base class it works.
As opposed to using the value in the drop down - "realization"
Warning, I'm still not recovered from my cold/flu (and had to take Friday off). I'm not in the best of moods - BUT THIS BUG HAS TO TAKE THE CAKE!
OK, thanks to the pointer Simon gave me I went to the Setting|UML... diaglog and tried to select the "offending" stereotype to make the change that Simon suggested. (As an aside - I thought this problem had been fixed YEARS ago when they changed the dropdown from realisation to realization).
When I try to select the offending item, I can't!
ALL items in the Settings UML... dialog with "Applies to" set to realization won't load. You get an empty set of attributes with just realization in the applies to box.
So I can''t change it!But wait, there's more! The observant among you may recall that I had SOME relaization entries that worked and was questioning why my latest ones didn't. How can this be when
none of them load?
So I go to the database and discover that the ones that work are stored in the DB as
realisations (because they went in BEFORE the dropdown was changed - but they are displayed in the dialog as
realization.
How are we poor users supposed to to make sense of this EAUI?
We were consistently told by our parents and grandparents that two wrongs DON'T make a right - here's example of why. (Or maybe since there's three wrongs - I think; all bets are off...)
Can we get this fixed for the next release?
Paolo
(OH, and to add insult to injury, the Project integrity says everything is OK...)
(Nearly forgot!) If you DO go into the database and change the value from realization to realisation it WILL fix the orginal problem of it NOT appearing in the Realization sterotype dropdown list....
Consistency, Consistency, Consistency! TM Using EA in spite of EA, NOT because of it!TM
