Community
Participate
Working Groups
I have verified this on v3.0.1 and v3.1M6. In the CVS Repositories view, clicking on "Configure Branches and Versions..." for certain modules pops up a window with empty areas named "Browse files for tags" and "New tags found in the selected files." This makes it impossible to checkout specific revisions of these modules. Either allow a tag to be entered manually (rather than force it to be discovered) or fix the parsing of the CVSROOT/modules file so that it correctly identifies the files belonging to modules with complex definitions. An example of a complex definition from the modules file is: my_proj app/proj/main &_src_part1 &_src_part2 _src_part1 -d src/com/sample/ app/proj/src _src_part2 -d src_extra/com/sample app/proj/src_extra Note that other modules from the same repository can have their tags discovered automatically via the above process. It is only the modules like the one just listed that have this problem. Other bugs in this Bugzilla database that appear related to this one are #68491 and #79077.
Both of your solutions would be valid. Another solution would be to allow the user to browse the entire repo in this case and select an appropriate file. This would require the user to know what the module mapped to so an appropriate file could be picked. Workaround is to checkout the module and then perform a Replace with Branch of Version.
Thanks for the tip. It works, to an extent. One weirdness is that if you "checkout" a tagged version in this way (by using Replace With > Another Branch or Version...), if the revision number of a file doesn't change, then the $Name$ keyword is not updated with the new tag. I have tested this only with v3.0.1. A workaround (for tagged files with multiple revisions) is to replace the file with a tag representing an older revision, then replace it again with the tag that I actually want.
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.
