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

Bug 67207

Summary:	[watch/edit] cvs checkout wizard not usable out of the box
Product:	[Eclipse Project] Platform	Reporter:	Dani Megert <daniel_megert>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dani Megert

2004-06-15 06:51:33 EDT

Test Pass for 3.0 RC2

1. Start fresh workspace
2. File > New > Checkout Project from CVS (need to enable all wizards)

Observe: there's no option to enable watch/edit. I have to dismiss the wizard
and go to the preference first.

Comment 1 Jean-Michel Lemieux

2004-06-15 08:42:35 EDT

If you guys are using CVS watch/edit to run validateEdit tests please consider
using the o.e.team.examples.filesystem pessimistic repository provider instead.
The watch/edit support in CVS was contributed by someone else and we never
really use it, plus it doesn't exercise the validateEdit scenarios enough (e.g.
coverage).

Instead, the pessimistic provider has a preference page that you can configure
to test certain scenarios, such as new content being fetched from the server on
validateEdit, validateEdit failing...

Comment 2 Dani Megert

2004-06-15 08:59:04 EDT

>If you guys are using CVS watch/edit to run validateEdit tests please consider
>using the o.e.team.examples.filesystem pessimistic repository provider instead.
I tested out-of-the box downloaded Eclipse SDK. I don't think any user actually
knows (or cares) about the fact that watch/edit was contributed by someone else
-  at least I did not know. Also, the preference pages does not give any hint on
this as well.

Do you want to say that CVS watch/edit though being part of Eclipse SDK is not
supported by Eclipse?

Comment 3 Jean-Michel Lemieux

2004-06-15 09:34:36 EDT

I didn't way it isn't supported, just not tested as much because only a small
group of CVS users actually use it. Statisticaly it isn't tested much because no
one uses it. I don't use it, because I hate the idea of hitting the server for
each edit, and that is what most people using CVS think as well.

Now, if you case about testing editor/refactoring calling validateEdit, then the
pessimistic provider should be used.

Comment 4 Eclipse Webmaster

2019-09-06 15:32:59 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 5 Eclipse Genie

2021-12-27 18:26:19 EST

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.