Enumerations not converted (EA 10 beta)

[Geert Bellekens]

In EA 10 enumerations are now a proper element type instead of a  stereotyped class.
The release notes state:
http://All existing enumerations handled to match previous version.

Does anyone know what that means? It certainly doesn't convert my existing classes with stereotype enumeration to the new enumerations.
That means that as we start using EA 10 we will have a mix of old and new flavor enumerations in the model :-/

Geert

[Eve]

Basically, EA will treat both types exactly the same way.

While we could update all previous enumerations, and may need to do that in the future, for now leaving existing ones alone provides a few advantages including that we don't need to enforce a full database upgrade. There is still compatibility between versions (for existing elements)

[Takeshi K]

Hi Simon and all,

I do not think 'EA will treat both types exactly the same way' on Beta 1.

Because:
- icons in the Project Browser are different
- 'old' Enumeration is still class, EA does not find by my own search rule 'ElementType = 'Enumeration'
- Quicklinker rules are different
- Relationship matrix does not show both enumeration for Type = 'Enumeration'
etc.

And 'new' enumeration is not shown in V9.3 Project Tree.

It may be possible to treat completely 'the same' for all features in EA before final V10 release, but it is difficult to be perfect. I think EA should convert all Enumerations (and Trace connector) to new and update the Database version.

It will lose compatibility, but it will be able to avoid many confusions in the future.

[qwerty]

Shouldn't there be some kind of migration utility included in EA (or as separate tool)? Maybe a simple script provided by Sparx.

q.