CVS with momentics in QNX 6.3

Hi, I am using Momentics and CVS server (windows box). Everything
works ok when commiting and updating and synchronizing to check
conflicts etc… but how can we setup CVS or Momentics so that they
can be notified if two different users checks out the same project
from the CVS server. It seems like from momentics point of view, who
ever commits the project last has to deal with conflicts… but if two
developers knew that they where working on the same project, maybe one
can work on another project. Any suggestions?

Use Watch/Edit (Window/Preference/Team/CVS/Watch/Edit). This way, if you
try to “Edit” a file which is already being edited by another user, you will
be notified. Please note that everybody accessing the CVS repository should
have this option enabled in order to work properly. You will also have to
chmod -R your files as you cannot “Edit” a file which is not read only.

Richard

“jinma” <matthew.jin@fmcti-dot-com.no-spam.invalid> wrote in message
news:d7lome$90i$1@inn.qnx.com

Hi, I am using Momentics and CVS server (windows box). Everything
works ok when commiting and updating and synchronizing to check
conflicts etc… but how can we setup CVS or Momentics so that they
can be notified if two different users checks out the same project
from the CVS server. It seems like from momentics point of view, who
ever commits the project last has to deal with conflicts… but if two
developers knew that they where working on the same project, maybe one
can work on another project. Any suggestions?

jinma wrote:

Hi, I am using Momentics and CVS server (windows box). Everything
works ok when commiting and updating and synchronizing to check
conflicts etc… but how can we setup CVS or Momentics so that they
can be notified if two different users checks out the same project
from the CVS server. It seems like from momentics point of view, who
ever commits the project last has to deal with conflicts… but if two
developers knew that they where working on the same project, maybe one
can work on another project. Any suggestions?

This is pretty much the way CVS works. Before attempting a check-in,
you should always do an update and resolve any conflicts.

In theory, this shouldn’t be much of a problem, unless the two
developers end up working on the same hunk of code for some reason… in
that case, you definitely want to see a conflict, because someone will
have to make a decision about which version of the code is correct.

Two developers working on the same code in the same file should be a
rare occurrence.


Chris Herborth (cherborth@qnx.com)
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - http://www.qnx.com/news/forms/newsletter.html