| whether this feature is included in eclipse [message #437425] |
Fri, 04 June 2004 11:28  |
Eclipse User |
|
|
|
Originally posted by: ssequeira.icope.com
Hi.Here is my problem situation
Suppose 2 devlopers have taken latest file say
Version1.1(checkout)from CVS.One of them made some changes and checked
in(commits) resulting in file version 1.2.But the other guy is still using
1.1.Now this guy having older version1.1 wants to commit,he will get an
error/conflict.Bcos there is a mismatch betwen file versions.
Now wat i want is:
A plugin that will tell/indicate me in advance (before commiting) that
this file(version 1.1)is already commited,instead of later coming to know
that a conflict has occured whenever he commits.
The advantage of this solution is:
1.If i know in advance that file has already been commited by some other
person,then i will take latest version from CVS.This will save
considerable amount of time to resolve the conflicts later.
2. Imagine iam on leave for 1 day.when i come the next day,by that time
many persons would have commited many modifications.Iam not aware of
these changes and straightway do my work with the old version which i
had the day before taking leave.If i have a plugin that will tell me,"The
file u r using is already commited" it will relieve me from all the
conflicts resolving procedures.
Is there any feature like this in eclipse CVS.Say the file name can
b marked in different color indicating that the current working file is
already committed.
Regards,
Steven Sequeira
|
|
|
| Re: whether this feature is included in eclipse [message #437428 is a reply to message #437425] |
Fri, 04 June 2004 14:07  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.forritan.net
steven sequeira wrote:
>
> 2. Imagine iam on leave for 1 day.when i come the next day,by that time
> many persons would have commited many modifications.Iam not aware of
> these changes and straightway do my work with the old version which i
> had the day before taking leave.
>
Well, wouldn't that be your choise - *not* to synchronize before you
went on with your work?
And besides that - I actually find that the update (and merge) facility
is already quite good, so I really don't see the problem - or value,
because what would you do if someone changes some file - and you are
notified - while you are typing on the same version? Do you toss your
modifications away and wait until your colleague is finished - or will
you rather merge the file if you are the one with the latter commit?
There are other versioning systems where you lock the files that you
check out - I have tried to work with something like that and I must say
that I will go with the CVS way anytime! It just a pain in b... when
someone has forgotten to release a file - and they are away for two
weeks... ;-)
|
|
|
| [cld u clarify a bit] whether this feature is included in eclipse [message #437431 is a reply to message #437428] |
Fri, 04 June 2004 14:20 |
| Eclipse User |
|
|
|
Originally posted by: ssequeira.icope.com
Hi,thanks for reply.
According to u,eclipse helps me in wat i want as i said.Will
synchronize option help me in this regard.since u have worked with CVS u
can tell me.Iam a novice to this field.
Thanks
Regards
steven
Eyðun Nielsen wrote:
> > Well, wouldn't that be your choise - *not* to synchronize before you
> went on with your work?
> And besides that - I actually find that the update (and merge) facility
> is already quite good, so I really don't see the problem - or value,
> because what would you do if someone changes some file - and you are
> notified - while you are typing on the same version? Do you toss your
> modifications away and wait until your colleague is finished - or will
> you rather merge the file if you are the one with the latter commit?
> There are other versioning systems where you lock the files that you
> check out - I have tried to work with something like that and I must say
> that I will go with the CVS way anytime! It just a pain in b... when
> someone has forgotten to release a file - and they are away for two
> weeks... ;-)
|
|
|
| Re: [cld u clarify a bit] whether this feature is included in eclipse [message #437435 is a reply to message #437431] |
Fri, 04 June 2004 16:25 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.forritan.net
If you are going to modify a file you can always (*if* *you* *know*
*that* *you* *have* *not* *modified* *it* *yet*) first refresh it from
the CVS repository with an update (right click -> Team -> Update)
You might also want to look into the tutorials:
e.g.: Help -> Help Contents -> Workbench User Guide -> Getting started
-> Team CVS tutorial.
and I did also find this article rather good:
http://www.eclipse.org/articles/Article-CVS-branching/eclips e_branch.html
Regards,
Eyðun
steven sequeira wrote:
> Hi,thanks for reply.
> According to u,eclipse helps me in wat i want as i said.Will
> synchronize option help me in this regard.since u have worked with CVS u
> can tell me.Iam a novice to this field.
>
> Thanks
>
> Regards
> steven
>
>
>
>
> Eyðun Nielsen wrote:
>
>
>>>Well, wouldn't that be your choise - *not* to synchronize before you
>>
>>went on with your work?
>
>
>>And besides that - I actually find that the update (and merge) facility
>>is already quite good, so I really don't see the problem - or value,
>>because what would you do if someone changes some file - and you are
>>notified - while you are typing on the same version? Do you toss your
>>modifications away and wait until your colleague is finished - or will
>>you rather merge the file if you are the one with the latter commit?
>
>
>>There are other versioning systems where you lock the files that you
>>check out - I have tried to work with something like that and I must say
>>that I will go with the CVS way anytime! It just a pain in b... when
>>someone has forgotten to release a file - and they are away for two
>>weeks... ;-)
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03467 seconds
] 
Search
Help
Register
Login
Home
