CVS problem

We just hooked in IntelliJ to CVS, pointing to the WinCVS client.
There are 2 issues:
1. When we commit a changed file through IntelliJ, the commit goes to CVS as
expected, but the file remains writable. Is there some way to get IntelliJ
to make the file read-only after a commit?

2. When you try to edit a read-only file that is in CVS, IntelliJ politely
tells you that the file is read-only and asks you if you want to invoke the
CVS edit command. However if you answer yes, it asks again. If you answer
yes again, it asks yet again. Then, on the 3rd 'yes' it opens the file for
editing.

(It does not always behave this way, sometimes it works on the first try.)

Thanks/Victor

(Please copy a reply to my email: mailto:vgrazi@caxton.com )



1 comment
Comment actions Permalink

The asking yes a few times I've noticed it happen when you import or
extend another class, it seems to want to edit all the files at the same
time, just in case you want to do editing in there too, but it doesn't
make sense to do that way. I haven't tested the new rev, so I didn't
report this as a bug yet. I would.

R

Victor Grazi wrote:

We just hooked in IntelliJ to CVS, pointing to the WinCVS client.
There are 2 issues:
1. When we commit a changed file through IntelliJ, the commit goes to CVS as
expected, but the file remains writable. Is there some way to get IntelliJ
to make the file read-only after a commit?

2. When you try to edit a read-only file that is in CVS, IntelliJ politely
tells you that the file is read-only and asks you if you want to invoke the
CVS edit command. However if you answer yes, it asks again. If you answer
yes again, it asks yet again. Then, on the 3rd 'yes' it opens the file for
editing.

(It does not always behave this way, sometimes it works on the first try.)

Thanks/Victor

(Please copy a reply to my email: mailto:vgrazi@caxton.com )



0

Please sign in to leave a comment.