| Author |
Message |
|
|
|
Post subject: CVS commit error since update from 3.8.2 to 3.8.3
Posted: Dec 16, 2004 - 03:56 PM
|
|
Registered Member


Joined: Sep 14, 2004
Posts: 45
|
|
After updating from version 3.8.2 to 3.8.3 I can no longer commit changes to CVS. I can still do check-outs, but cannot add new files or commit changes to existing ones. I have tried big and small files as well as ascii/binary. Nothing commits.
I tested CVS outside of the IDE and it works fine. Please help. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Dec 16, 2004 - 04:10 PM
|
|
Registered Member


Joined: Sep 14, 2004
Posts: 45
|
|
OK, I found the problem, but need to know how to handle this in the future. I have several branches and versions. After I upgraded, I versioned my code. I am now showing that I am working on the new version. But I can't commit changes to a version. Error is "cvs server: sticky tag `v3_6_0_2' for file `WEB-INF/.struts-config.mex' is not a branch".
But if I try to switch to the branch, it warns that it will delete my changes. For now I am going to copy the changes to another directory and switch, then copy back. But how do I handle this in the future?? I create versions so I can go back to a version and make bug fixes. but I need to be able to save these fixes. Do I have to create a new branch every time? This is not the way I thought this would work.
Any ideas on how I am supposed to be using CVS with the IDE would be greatly appreciated. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Dec 16, 2004 - 04:33 PM
|
|
Registered Member

Joined: Jan 06, 2004
Posts: 23824
|
|
Moving to OT > Soft Dev, this is a CVS question
ON a side note, I never tag/branch beacuse I don't understand CVS's interpretation of the process completely... it seems overly complex to me. I will ask our devs if they know though. |
_________________ Riyad
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Dec 16, 2004 - 04:44 PM
|
|
Registered Member


Joined: Sep 14, 2004
Posts: 45
|
|
Thanks. I thought I understood it, but apparently not. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Dec 16, 2004 - 05:21 PM
|
|
Moderator


Joined: May 06, 2003
Posts: 6760
|
|
Basically, you need to create a branch and begin working in it apriori. It becomes very difficult, as you've found, to make a bunch of changes and then decide "I should put this on a branch". After you check in your changes on the branch, you can move any tags, as needed. |
_________________ --Scott
MyEclipse Support
|
| |
|
|
|
 |
|
|