|
Re: Package merge question [message #474500 is a reply to message #474396] |
Sat, 21 July 2007 17:07 |
Lutz Wrage Messages: 181 Registered: July 2009 |
Senior Member |
|
|
Lutz Wrage wrote:
> I want to use package merge for a meta-model I'm developing. I tried a
> simple example in the uml editor. I create a package P with class A, and
> another package M. M merges P. Now I execute the package merge using
> the editor action, and everything works as expected. M now contains a
> class A. However, the package merge element has been removed from M, and
> has been replaced by some annotation.
>
> When I now make a change to A in P (or any change to P, maybe add a
> class) how do I get this change into M? I can't do the package merge
> again, because the package merge element isn't part of M any more. When
> I re-create a package merge child element in M, I can execute the merge
> and the updates made in A are copied into M. This seems to be quite
> tedious during model development because there will be many changes. Is
> there a way of simplifying this process?
>
> Or is it a bug that merging removes the package merge element from the
> receiving package?
>
> Thanks,
> Lutz
Answering my own question: I found that merge works recursively, so it
seems I only need to call merge for one package and save the result in a
new file.
- Lutz
|
|
|
Re: Package merge question [message #623934 is a reply to message #474396] |
Sat, 21 July 2007 17:07 |
Lutz Wrage Messages: 181 Registered: July 2009 |
Senior Member |
|
|
Lutz Wrage wrote:
> I want to use package merge for a meta-model I'm developing. I tried a
> simple example in the uml editor. I create a package P with class A, and
> another package M. M merges P. Now I execute the package merge using
> the editor action, and everything works as expected. M now contains a
> class A. However, the package merge element has been removed from M, and
> has been replaced by some annotation.
>
> When I now make a change to A in P (or any change to P, maybe add a
> class) how do I get this change into M? I can't do the package merge
> again, because the package merge element isn't part of M any more. When
> I re-create a package merge child element in M, I can execute the merge
> and the updates made in A are copied into M. This seems to be quite
> tedious during model development because there will be many changes. Is
> there a way of simplifying this process?
>
> Or is it a bug that merging removes the package merge element from the
> receiving package?
>
> Thanks,
> Lutz
Answering my own question: I found that merge works recursively, so it
seems I only need to call merge for one package and save the result in a
new file.
- Lutz
|
|
|
Powered by
FUDForum. Page generated in 0.04239 seconds