Bug 30503 - IPackageFragmentRoot:move, copy should accept null as sibling
Summary: IPackageFragmentRoot:move, copy should accept null as sibling
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-29 09:34 EST by Adam Kiezun CLA
Modified: 2003-02-10 12:53 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Kiezun CLA 2003-01-29 09:34:08 EST 
20030128
ISourceManipulation accepts null as sibling
IPackageFragmentRoot seems not to (by looking at the API)

same for copy
Comment 1 Jerome Lanneluc CLA 2003-01-29 10:18:25 EST 
From the javadoc, of IPackageFragmentRoot.move(...):
If <code>null</code> is specified, the classpath entry is added at the end of 
the destination project's raw classpath.
Comment 2 Adam Kiezun CLA 2003-01-29 10:34:29 EST 
i looked at @param
Comment 3 Jerome Lanneluc CLA 2003-01-29 11:06:21 EST 
Changed @param to:
* @param sibling the classpath entry before which a copy of the classpath
* entry should be inserted or <code>null</code> if the classpath entry should
* be inserted at the end
Comment 4 David Audel CLA 2003-02-10 12:53:32 EST 
Verified.