- This topic has 26 replies, 8 voices, and was last updated 16 years, 7 months ago by
.
-
Posts
-
@support-rkalla wrote:
Paul,
These fixes will all be in 5.5, we have an M1 release due out in 2 weeks. Be sure to beat it to death to make sure we got it right when we release it.Hello again Rkalla,
I have installed myEclipse 5.5 M1 and cut and paste between diagrams is fixed, however I can’t find a way to cut and paste between two UML repositories. I’ve even tried exporting as XMI then re-importing into the other repository. The classes come in however, you get another instance of the same package created that contains the classes. ala
com.company.subject.class1
com.company.subject.class2
com.company.subject.class3
com.company.subject.class4
com.company.subject.class5imported will create a new package with the same name as an existing package of the same name and all the imported classes end up in the new package directory separate to the existing classes in the existing package of the same name. Theres no way to drag classes from one package into the other package. This is a BUG.
Cutting and pasting between repositories just does not work. OMMISSION
Regards,
Paul Cahill
BTW, has the project manager had time to re-consider my proposal?The copy/paste support is a work in progress. Copy between repositories will be worked on.
There is a real problem with import XMI. I filled a PR about it.Copy paste of classes between packages can be done in the outline. Or it can be modified in the class properties (the namespace field).
@support-luc wrote:
The copy/paste support is a work in progress. Copy between repositories will be worked on.
Why is there more than one repository per project? If the domain is that different, then it makes more sense to create a new project instead of a repository
There is a real problem with import XMI. I filled a PR about it.
I take it you mean that the problem I’m reporting will be listed in the bug track?
Copy paste of classes between packages can be done in the outline. Or it can be modified in the class properties (the namespace field).
Only if the packages are in the same repository. If you’ve made the mistake of developing your models in two repositories (which is my case), then the only way to merge them is to generate code then reverse engineer them into the a new diagram, not exactly inefficient lots of detail about the diagrams (comments etc) are lost.
This is a very frustrating issue which should not be difficult to resolve. Can this be aded to the next release?For example, I have finish a sequence diagram and another one is just similar to this one and I want to make a copy of the current one so I can just modify it later. With the latest version, I cannot find any copy diagram option. I also cannot create a blank document and copy the sequence diagram over. Please consider this as the basic function is your future release.
