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

Bug 232990

Summary:	[extract class] Extract class does not do a CVS edit notification
Product:	[Eclipse Project] JDT	Reporter:	Benno Baumgartner <benno.baumgartner>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	martinae
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Benno Baumgartner

2008-05-20 10:54:12 EDT

I20080516-1333

1. Check-out code from the repository in CVS Watch/Edit mode (stores file in read-only mode)
2. Do Refactor>Extract Class... on such a resource
Is:
 Refactoring fails with a fatal error: File is read-only. Also the refactoring does make the file writable.
Should:
 Show dialog that 'A CVS edit notification is required', make the file writable and perform the refactoring, like i.e. rename does.

Comment 1 Martin Aeschlimann

2008-05-21 09:20:13 EDT

I tried with the pessimistic simple provider: The refactoring correctly prompted to check out before opening the dialog.

Comment 2 Martin Aeschlimann

2008-05-23 08:51:47 EDT

I also tested with CVS Watch/Edit and didn't see a problem. The files were automatically checked out, no error dialog. Benno, if you have steps, please add them here.

Comment 3 Benno Baumgartner

2008-05-26 04:13:11 EDT

(In reply to comment #2)
> I also tested with CVS Watch/Edit and didn't see a problem. The files were
> automatically checked out, no error dialog. Benno, if you have steps, please
> add them here.
> 

On Watch/Edit preference page I set:
Configure projects to use Watch/Edit
Enable temporary watches on edit
Send a CVS edit notification to the server
Always prompt
Prompt to update if out of date

Comment 4 Eclipse Genie

2019-09-08 12:39:04 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.

--
The automated Eclipse Genie.