Convenient way to automate conversion of Local Modules to TeamServer modules?

General discussions about teamwork

Moderator: Moderators

Convenient way to automate conversion of Local Modules to TeamServer modules?

Postby Lonnie VanZandt » Tue Feb 03, 2009 1:31 pm

What is the recommended sequence for evolving a legacy file-stored Model
with Local Modules to a TeamServer Project with TeamServer Modules such that
the final project has no Local Modules, TeamServer stores the Project and
all the formerly Local Modules, and no relationship information between the
model and the modules is broken?

I managed to migrate one such model but it took a few Oops corrections until
everything appears to have migrated correctly.


Lonnie VanZandt
 
Posts Rating:

Re: Convenient way to automate conversion of Local Modules to TeamServer modules?

Postby Donatas Simkunas » Wed Feb 04, 2009 7:17 am

We recommend to review all Modules in "Local Modules" tab in the "Commit
Settings" dialog. This dialog is shown before commit project. Normally when
working with teamwork project this must be done only one time - when adding
project to teamwork, or when new local module was used.

Regards

--
Donatas Simkunas
Senior Developer
No Magic Europe
Savanoriu pr. 363, LT 49425 Kaunas
Phone: +370 37 324032 Fax: +370 37 320670
WWW: http://www.magicdraw.com
On Wednesday 04 February 2009 11:05:58

Donatas Simkunas
 
Posts Rating:

Re: Convenient way to automate conversion of Local Modules to TeamServer modules?

Postby Lonnie VanZandt » Thu Feb 05, 2009 11:16 am

That seems intuitive--however, sometimes, some Local Modules refuse to
promote themselves to TeamServer modules even when so instructed. There is
no notice reported when the Add to TeamServer select fails to be honored.
One discovers that the Modules remain Local on the next Commit attempt...


Lonnie VanZandt
 
Posts Rating:

Re: Convenient way to automate conversion of Local Modules to TeamServer modules?

Postby Donatas Simkunas » Fri Feb 06, 2009 6:55 am

Hello,

There can be different scenarios when local module appears again as local on
next commit.
One way when that happens is that some actions starts using local module
again, and does it without any warnings. For example code engineering, or
custom diagrams may use local module even for teamwork project.

Another situation is that even after commit module remains local. If you have
such situation please give more details about it.

Regards

--
Donatas Simkunas
Senior Developer
No Magic Europe
Savanoriu pr. 363, LT 49425 Kaunas
Phone: +370 37 324032 Fax: +370 37 320670
WWW: http://www.magicdraw.com
On Friday 06 February 2009 10:03:19
nntp://news.nomagic.com/nomagic.products.magicdrawuml.teamwork wrote:
> That seems intuitive--however, sometimes, some Local Modules refuse to
> promote themselves to TeamServer modules even when so instructed. There is
> no notice reported when the Add to TeamServer select fails to be honored.
> One discovers that the Modules remain Local on the next Commit attempt...

Donatas Simkunas
 
Posts Rating:


Return to Merging, branching, modules, team collaboration

Who is online

Users browsing this forum: No registered users and 0 guests