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

Bug 230840

Summary:	Relative path is inconsistent
Product:	z_Archived	Reporter:	Frank Zhang <xiong.zhang>
Component:	BIRT	Assignee:	Birt-Report-inbox <Birt-Report-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	rlu
Version:	2.3.0
Target Milestone:	2.3.0 RC1
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	176543

Description Frank Zhang

2008-05-07 05:00:19 EDT

As we know, when opening file in resource folder, we use relative path instead of full path.

SessionHandle.openLibrary(relativeLibraryName) can open a library file in resource folder, that's good.
In ElementExportUtils.exportElements(elementsToExport, libraryFileName, boolean), if libraryFileName exists in resource folder, the element can be exported to it. But if the file doesn't exist, the created library file is in neither current project folder nor resource folder, but in eclipse system home folder. That's inconsistent.

Could you please correct this soon, for a RC1 bug depends on it.

Comment 1 Rick Lu

2008-05-07 05:26:16 EDT

For relative path case, Model shouldn't save the file. Will get issues for Resource Path. The outside caller is better to pass the absolute path into API.