Bug 6907

Summary:	API: IFile.appendContents spec does not mention non-local
Product:	[Eclipse Project] Platform	Reporter:	Jim des Rivieres <jeem>
Component:	Resources	Assignee:	DJ Houghton <dj.houghton>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	api
Version:	1.0
Target Milestone:	2.0 M6
Hardware:	PC
OS:	Windows 98
Whiteboard:

Description Jim des Rivieres

2001-12-13 14:39:16 EST

The spec for IFile.appendContents spec does not 
mention what happens when the file is non-local.

It should fail indicating the file is non-local.

Comment 1 DJ Houghton

2002-05-03 09:38:00 EDT

Spec mentioned that if FORCE=true then the contents are appended and the 
resource is marked as being local even if it wasn't before.

Is this correct?

Comment 2 Jim des Rivieres

2002-05-03 10:57:15 EDT

If force=true, IFile is non-local, file exists in local file system:
make IFile local, append contents (the thinking being that this file,
though marked non-local, was in fact local awaiting discovery; so 
force=true says we it is ok to make file local and proceed as per normal)

If force=true, IFile is non-local, file does not exist in local file system:
fail - file not local (this file is not local for real - cannot append
something to a file that you don't have)

If force=false, IFile is non-local, file exists in local file system:
fail - file not local

If force=false, IFile is non-local, file does not exist in local file system:
fail - file not local

Comment 3 DJ Houghton

2002-05-20 21:58:18 EDT

Clarified spec.
Updated tests.
Fixed implementation. (bug found by new tests)
Released.