Community
Participate
Working Groups
CVS tags (a.k.a. project versions) that have not been created using rtag don't show up in the repository explorer because the history file on the server does not reference them. Current workaround: define a team stream using the same tag name, then you can browse the project version. This is less than optimal because it does not behave like a team stream - you cannot release anything to it... NOTES: KM (5/22/01 10:03:38 PM) This can occur for open source repos which have history turned off. Jean-Michel (11/06/2001 4:44:02 PM) Include the cvs error that is returned when trying to release to a stream that is really a version :) cvs server: sticky tag 'v1' for file a.txt is not a branch tag. Jean-Michel (6/13/01 9:59:17 PM) We should describe in the CVS docs that in order to browse or add a version of an existing CVS project that was not created using rtag users should create rtag version using the cvs command line. We should probably not mention anything about the creating a stream hack? Jean-Michel (8/23/01 10:24:09 AM) Many Eclipse VCM operations rely on project versions being available. For example, without them you cannot merge, compare/replace project versions, and create a new stream (copy version to stream). That means that any open source project that has disabled history would not be able to use much of the functionality in Eclipse VCM. I suggest the following CVS specific features be added to the CVS adapter: 1. A mechanism for defining a project version by name on CVS projects. This would be a name not validated until an operation is performed (e.g. load, browsing). The names would be workspace persistent, and allow using all Eclipse features which rely on version names. This resembles CVS' support for providing -r <version name> on the command line, we simply cache a set of -r parameters. 2. Add a CVS action to IFileEditions which allow creating project versions automatically based on the version tags already defined on the CVS file. This would be easy to do. Jean-Michel (9/14/01 1:36:14 PM) Fixed, released into HEAD.
Fixed in build 202a.
[Fixed in v202]
PRODUCT VERSION: 0.044