Bugzilla – Full Text Bug Listing
| Summary: | [Operations] Failure to move tag not reported to the user | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Matthew Conway <matt> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | stalebug | ||
If you look closely, you will notice that there is an "ok" nestled in amounst the trace you provided. Sometimes the CVS server maks it a bit difficult to know when an error occurs. The specific issue here is that CVS does not support the moving of branch tags when tagging local content. It does support it for remote but it is strongly discouraged by the CVS manual. For this case, we should detect that some files were not moved and point the user at the CVS console. Changing OS from Mac OS to Mac OS X as per bug 185991 This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
I did a Team->Tag as version... (move tag if exists) and it seemed to succeed. However I noticed that the tag did not in fact get moved, and there was an error in the cvs log. Somehow eclipse did not know there was an error (no dialog or progress error icon), so it probably needs to check for something extra - here are the relevant lines from the CVS log... Using cvs ext on eclipse 3.2RC1 osx 10.4.6 java 1.4.2_09 *** cvs tag -F -l "/tr-MAIN/PRODUCTION" "/tr-MAIN/site/nexus/skins/tools/appscreen.vm" "/tr-MAIN/site/nexus/skins/tools/edit.vm" cvs tag: site/nexus/skins/tools/appscreen.vm: Not moving branch tag `PRODUCTION' from 1.2 to 1.3. cvs tag: site/nexus/skins/tools/edit.vm: Not moving branch tag `PRODUCTION' from 1.4 to 1.5. ok (took 0:00.679) Error: The following warnings were reported while performing the "cvs tag" command. Error: tr-MAIN: cvs tag: site/nexus/skins/tools/appscreen.vm: Not moving branch tag `PRODUCTION' from 1.2 to 1.3. Error: tr-MAIN: cvs tag: site/nexus/skins/tools/edit.vm: Not moving branch tag `PRODUCTION' from 1.4 to 1.5. ***