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

Bug 356498

Summary:	Problems with EGLAR export
Product:	z_Archived	Reporter:	Justin Spadea <jspadea>
Component:	EDT	Assignee:	Xiao Bin Chen <xiaobinc>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	chenzhh, svihovec, zhuzhi
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	EGLAR Eglar

Description Justin Spadea

2011-09-01 12:57:29 EDT

1. If the IR directory is not EGLbin (e.g. it's eglbin or EGLBin) then you get a resource exception. NewEglarFileExportOperation.getBinFolder() needs to ask the IEGLProject what the output directory is.

2. For the Java source files it's looking in hard-coded locations, e.g. NewEglarFileExportOperation.EGL_GEN_JAVA_FOLDER, NewEglarFileExportOperation.getGenFolder(), and the code also references EGLProjectInfoUtility.getDefaultGeneratedJavaFolder(). In EDT a user can pick any directory they want for the generated files, and they can specify this at any level (project, EGLSource, package, or file). There is no single location for generated files.

Comment 1 Tony Chen

2011-09-06 22:12:54 EDT

We are not providing EGLar functions in 0.7. The export eglar function should be hidden, and this bug need to be triaged to future

Comment 2 Zhi Zhu

2012-04-17 04:44:38 EDT

Assign to XiaoBin since he will be responsible for EGLAR export/import wizards

Comment 3 Xiao Bin Chen

2012-04-19 23:15:14 EDT

Since we are not going to implement it now. Put it out of I1