Model Inconsitencies in EA

[jack89]

Hi,

I'm using Lemontree plugin in order to use EA with GIT. Every time that I open lemontree, it says that there are a lot of model inconsistencies and it suggest me to run the project integrity check from EA but EA doesn't find any model inconsistency.

If I show the log related to the inconsistencies found by lemontree, I noticed that the warning error is always like this one:

Branch: Base; 
Description: Xref of stereotype with Name 'TEST' doesn't contain Guid nor FqName.
ElementGuid: {AA6B6DC0-TC3T-4454-IOIE-045789B963B};
Category: Warning;
Error: 100012000000

My question is: how can I solve an inconsistency like this one? Which stereotype property is missing? Note that 'TEST' stereotype is a custom stereotype made by me.

Thank you in advance for your amazing support.
 

[qwerty]

You should go and ask that LieberLieber. They do have support, don't they?

q.

[Geert Bellekens]

For some reason the steroetype didn't register properly, possibly because it was set in a previous version (before 15.1) of EA that wasn't that strict with stereotypes yet.
The best you can do is remove the stereotype, save the element, and then re-apply the stereotype, that should fix that error.

Nowadays "loose" stereotypes like that are discouraged.
Preferably all stereotypes should be defined in a UML profile, that is (again preferably) deployed using an MDG technology.

Geert

[Paolo F Cantoni]

For some reason, the stereotype didn't register properly, possibly because it was set in a previous version (before 15.1) of EA that wasn't that strict with stereotypes yet.
The best you can do is remove the stereotype, save the element, and then re-apply the stereotype, that should fix that error.

Nowadays "loose" stereotypes like that are discouraged.
Preferably all stereotypes should be defined in a UML profile, that is (again preferably) deployed using an MDG technology.

Geert

Wot 'e sed!

Paolo

[Uffe]

For some reason, the stereotype didn't register properly, possibly because it was set in a previous version (before 15.1) of EA that wasn't that strict with stereotypes yet.
The best you can do is remove the stereotype, save the element, and then re-apply the stereotype, that should fix that error.

Nowadays "loose" stereotypes like that are discouraged.
Preferably all stereotypes should be defined in a UML profile, that is (again preferably) deployed using an MDG technology.

Geert

Wot 'e sed!

Paolo

When the user security permission for creating in-project stereotypes was introduced, you couldn't actually use it because some core function(s) weren't implemented with profiles but instead relied on being able to create stereotypes on the fly. Problem is, I can't remember which functions they were.

Are all EA's functions now cleaned up so that you can disable in-project stereotype creation without anything crapping out?

/Uffe

[Geert Bellekens]

For some reason, the stereotype didn't register properly, possibly because it was set in a previous version (before 15.1) of EA that wasn't that strict with stereotypes yet.
The best you can do is remove the stereotype, save the element, and then re-apply the stereotype, that should fix that error.

Nowadays "loose" stereotypes like that are discouraged.
Preferably all stereotypes should be defined in a UML profile, that is (again preferably) deployed using an MDG technology.

Geert

Wot 'e sed!

Paolo

When the user security permission for creating in-project stereotypes was introduced, you couldn't actually use it because some core function(s) weren't implemented with profiles but instead relied on being able to create stereotypes on the fly. Problem is, I can't remember which functions they were.

Are all EA's functions now cleaned up so that you can disable in-project stereotype creation without anything crapping out?

/Uffe

I've disabled that function for all but admins, and I haven't had any problems so far.

Geert