Reuse model element under version control

[Mercurius]

Hello,
I have difficulties to reuse a model element which is an a separated version controlled package. Maybe someone can help?

There are two packages:
- A package "Main Package" which includes a block "Context" and a diagram for its architecture
- A package "Module Package" which includes a block "Module" that shall become part of "Context"

Both packages are version controlled.

Now I do the following:
- Check out "Main Package"
- Put "Module" from "Module Package" (which is not checked out or locked by anybody) as a link on the diagram in "Main Package"
- Draw a "Part Association" from "Module" to "Context"

All that works well. And it should since I do not do any changes for "Module".

But now either one of the following happens:
a) After saving, closing and reopening the diagram, "Module" has been silently removed from my diagram OR
b) After a short moment message "The diagram has been modified by another user. It will remain locked against modification unitl it is reloaded." appears.  Whatever I click now, "Module" is removed.

How can I reuse "Module"? Since I am not working on "Module", I am also not allowed to check it out.

[Geert Bellekens]

- Draw a "Part Association" from "Module" to "Context"

This means you are actually changing Module, and that should not be allowed if you didn't check-out the package containing Module.

But there is no reason the element should be removed from your diagram.

I would try a project integrity check.

Geert

[Mercurius]

Hi Geert
Thank you for your quick answer.

I tried it with a different module without the Part Association. Just showing it on the diagram. Even then it is the same behavior. :-(

Integrity check did also not find anything suspicious.

Maybe it is a bug of the version control addin?

[Geert Bellekens]

Maybe it is a bug of the version control addin?

Which version control add-in are you using?
I was assuming you are using the build-in version control integration.

Geert

[Mercurius]

It is called "LimeJuice".

[qwerty]

What is that? A derivative of LemonTree??

q.

[Mercurius]

It seems to be some kind of legacy add-in, which is still used by my client.
Do you think that this add-in would be the origin of the mentioned problems?
(If the EA Guru confirms, I might have better chances to convince my client to change that.) 

Thanks and regards

[Geert Bellekens]

Without knowing the add-in there is no way we can confirm or deny if this add-in is the source of your problem.

All I can say is that version control isn't supposed to work like that.

Geert

[Takeshi K]

Hello Mercurius,

I have heard of a similar problem (EA's behaviour is the same) and if I remember correctly the problem has now been fixed.
If you are not using the latest build of version 16.1, it is worth trying the latest build.

[Mercurius]

Hello Takeshi K

The problem got even worse, but indeed after updating from build 1623 to 1628 it seems to be solved. Thank you very much for your idea.   

Mercurius