antbear-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Antbear-devel] UML tool


From: wolpers
Subject: Re: [Antbear-devel] UML tool
Date: 04 Nov 2002 13:50:07 +0100

On Mon, 2002-11-04 at 01:57, Adam Ferla wrote:
> Hey guys
> 
> Have we made a choice on what UML tool we are using. I downloaded Visual 
> Paradigm Community edition. The downside I have seen so far with this is 
> that it only allows 1 use case diagram per project. This will not be a huge 
> problem.
I did not know that.  But I also would consider this not to be a big
problem.  So unless one of you really decides against it I would prefer
to stick with visual-paradigm.
> 
> Also, I've been thinking why poseidon has been stuffing up. Could it be that 
> because CVS is designed with source files in mind when updating binary files 
> it tries to fix up conflicts between two versions of the binary files, in 
> doing so, it makes them unreadable (because binary files are not ASCII). 

> That might be why when you put a completely new zargo file on the cvs it 
> worked fine, CVS did not have to fix up any conflicts between the users' old 
> file and the new updated file.
> 
This could be the case.  You can tell CVS when checking in a new file
that it is a binary file to make sure it does not mess up the files.  I
thought about this, too, but none of the binary files I ever submitted
to CVS got corrupted.  In combination with the fact that the first
.zargo file you sent me via mail was also broken I blamed Poseidon to be
the bugger.
>From the web I could read that (even though they sell their product!)
Poseidon does have trouble saving projects without the loss of data
under certain circumstances.

We could use the 'cvs admin <some parameter>' command to switch already
checked in files to 'binary' if you prefer.  This of course makes only
sense if they have not yet been corrupted, like the visual-paradigm
files.

This brings me to another cvs point:  I thought about the idea of
setting cvs up that we get automatic mails whenever somebody checked
something in via cvs.  In the mail we get a list of files that have been
changed and, more important, we get to read the message the updating
person wrote about its updates.  I would like those mails to be sent to
the antbear-devel mailinglist, although we can set up another one if
someone does not want to get all those cvs mails.  Please note that
every 'cvs commit' would lead to one mail and that can sum up to quite a
few mails!
So please tell me if you want to have a separate mailinglist, that you
do not have to join, for the automatic cvs mails.  You could always
browse the archives if you wanted to.

- Thorsten








reply via email to

[Prev in Thread] Current Thread [Next in Thread]