Bug 356498 - Problems with EGLAR export
Summary: Problems with EGLAR export
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Xiao Bin Chen CLA
QA Contact:
URL:
Whiteboard: EGLAR Eglar
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-01 12:57 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:16 EST (History)
3 users (show)

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 Justin Spadea CLA 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 CLA 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 CLA 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 CLA 2012-04-19 23:15:14 EDT 
Since we are not going to implement it now. Put it out of I1