Bug 321941 - CVS function problem and reporting of it
Summary: CVS function problem and reporting of it
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-06 00:36 EDT by Dave Dyer CLA
Modified: 2019-09-06 15:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Dyer CLA 2010-08-06 00:36:40 EDT
Build Identifier: 20100617-1415

"Updating change sets for cvs has encountered a problem"

Errors occurred while updating the change sets for CVS Workspace
Invalid CVS repository location format: :local:f:\cvs\ddyer
Invalid CVS repository location format: :local:f:\cvs\ddyer
Location must have form ':methodname:[user[:password]@]host:[port]/path/to/cvsroot'
Only the following methods are supported: ext, extssh, pserver, pserverssh2


Reproducible: Always

Steps to Reproduce:
1. just have the right kind of repository
2.

It's odd that I've never seen this complaint before, as I've been using the
same repository for years.  

Two points about this are bugs in my view.

(1) in reporting this problem, you should cite the particular file
not just the repository format.

(2) you really ought to support :local: as a CVS access method.
Comment 1 Prakash Rangaraj CLA 2010-08-06 00:40:12 EDT
Moving to Team
Comment 2 Tomasz Zarna CLA 2010-08-17 07:46:40 EDT
(In reply to comment #0)
> It's odd that I've never seen this complaint before, as I've been using the
> same repository for years.

Have you been using that repo in Eclipse? If so, could you tell me which version of Eclipse was that? I don't remember if we've ever supported other connection methods then you mentioned in your comment.
Comment 3 Dave Dyer CLA 2010-08-17 12:47:01 EDT
The CVS information is not managed or used through eclipse.  I more or less
ignore eclipse capability to use it.  

It's possible that what changed here is one of the files, and eclipse was
trying to update some internal state, not knowing that I didn't expect it
to use CVS on this directory.

Notwithstanding, the directory in question has been under eclipse
purview "forever", and this is the first time eclipse has mentioned
anything about the cvs info.   And, :local access method is simple
and ought to be supported.
Comment 4 Tomasz Zarna CLA 2010-08-19 04:11:19 EDT
Are you saying that you have a CVS shared project in your workspace, but it has been checked out by a third party tool (not Eclipse) from :local:f:\cvs\ddyer? If so, does it mean that the project is not decorated as shared in Eclipse (little orange cylinder in the bottom right) and no team operations (like Team > Synchronize, Team > Commit) can be executed on it?
Comment 5 Dave Dyer CLA 2010-08-19 13:46:25 EDT
The project was checked out and normally maintained using Tortoise CVS.
Team operations are available, and individual files have CVS annotations
and operations...

I didn't do anything special to enable or disable CVS operations for
this project, eclipse seems to have discovered the CVS directories for
itself.

That is, generally.  Also, generally, the project is checked out with
:pserver:, but this project has a lot of history, and a lot of ad-hoc
rearrangements have been made over time.  It's quite likely that the
directory that caused the complaint was checked out using :local: and
copied here. 


One of the weaknesses of CVS in general is that it doesn't have any
notion of subprojects or included projects, so these ad-hoc copies 
of partial hierarchies are expedient.

It would help if the message had said what file it was complaining about.
Comment 6 Tomasz Zarna CLA 2010-08-23 07:04:59 EDT
(In reply to comment #5)
> It would help if the message had said what file it was complaining about.

Agree. Except the error dialog, have you noticed any entries in the Error Log? Something similar to this maybe:

org.eclipse.team.internal.ccvs.core.CVSException: Invalid CVS repository location format: :local:user@host:/BUGS
	at org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.fromString(CVSRepositoryLocation.java:238)
	at org.eclipse.team.internal.ccvs.core.util.KnownRepositories.getRepository(KnownRepositories.java:181)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.extractContainerProperties(CVSLightweightDecorator.java:359)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:319)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:241)
	at org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.decorate(CVSLightweightDecorator.java:161)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Contains: Location must have form ':methodname:[user[:password]@]host:[port]/path/to/cvsroot'
Contains: Only the following methods are supported: ext, extssh, pserver, pserverssh2, test
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:38:28 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.