Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 112249

Summary:	[Tag RelEng] Tagging from release tool does not work on deleted files
Product:	[Eclipse Project] Platform	Reporter:	Douglas Pollock <douglas.pollock>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Douglas Pollock

2005-10-11 15:42:52 EDT

There is an inconsistency in the behaviour from the release tool, and I guess 
from the tagging behaviour in CVS.  I believe this is how CVS actually works, 
so I guess I shouldn't be all that surprised.  But wrapped in my warm IDE 
bubble, it did manage to shock me. 
 
If I apply a patch which contains changes to files, I can then tag those 
files.  The revision of the file that will be tagged is the revision which I 
had last retrieved from CVS.  So, if I checked out revision 1.10 of a file 
from CVS, and then make changes to that file and tag it, revision 1.10 of a 
file will be tagged in CVS. 
 
If a patch contains file additions, I can try to tag those files.  No revision 
exists in CVS, so no revision will be tagged.  This is the same as above: the 
revision I last checked out from CVS (i.e., none) will be the one that gets 
tagged. 
 
If a patch contains file deletions, I can try to tag those files.  I expect 
the same thing to happen: the last revision I checked out from CVS should be 
tagged.  Unfortunately, that's not what happens.  The file is not tagged at 
all. 
 
 
Extra: The releng tool should be aware of this limitation and refuse to tag a 
workspace where there is a pending deletion.

Comment 1 Eclipse Webmaster

2019-09-06 16:18:21 EDT

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.

Comment 2 Eclipse Genie

2021-10-26 16:04:02 EDT

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.