Bug 30522

Summary:	IPackageFragmentRoot: move, copy updateClasspath semantics
Product:	[Eclipse Project] JDT	Reporter:	Adam Kiezun <akiezun>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.1
Target Milestone:	2.1 M5
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Adam Kiezun

2003-01-29 12:44:20 EST

20030128
it makes little sense not to update the classpath of the destination 
project (if you don't, then you basically copy a folder or a zip file - not 
useful)

so i'd vote for changing the semantics of the updateClasspath flag to 
refer only to classpaths of projects referencing the IPackageFragmentRoot

more trivial case i copy:
for copy, i think you always want to pass 'true'

Comment 1 Adam Kiezun

2003-01-30 05:19:52 EST

another issue is the semantics of that flag for delete:
i think one always wants to update the classpath of the project that is the 
parent of the packageFragmentRoot (cannot find a case where that would be not 
desirable)

Comment 2 Adam Kiezun

2003-01-30 09:31:02 EST

another issue:
when the destination project is not a java project, then you're not allowed to 
pass 'true' as the updateClasspath argument.
but then you're left with errors because classpath gets out of synch

Comment 3 Jerome Lanneluc

2003-02-02 06:24:24 EST

These operations can now fine-grained control how the classpaths are updated 
using the updateClasspath flags.