| Summary: | The compiler preferences need to be updated to allow the configuration of options | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Joseph Vincens <jvincens> | ||||
| Component: | EDT | Assignee: | Tony Chen <chenzhh> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | chenzhh, greer, jeffdouglas, margolis, mheitz, tww | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Joseph Vincens
*** Bug 355538 has been marked as a duplicate of this bug. *** Looking at the compiler preference. Need to refine the code a bit so a new parameter (generatorArgument) can be added. Created attachment 202741 [details]
Patch for generation arguments
Patch for generation arguments
Joe, Jeff, attached is a patch for the proposed changes to support generation arguments, please review it. Major changes: - Added a text field in generator setting tab to allow user input "Generation arguments". This field is only available in project and resource scope. (you can not set generation argument across workspace) - Generation argument will be saved to preference (like we did for generation directory) - add convenient method getGenerationArgument(IResource resource) in AbstractGenerator to fetch the save argument Questions: - Do we need to set default generation argument for the workspace? - Is is ok to allow any string to be input? Is any format check necessary? In this release, the preferences page should allow any input string and not do any format checking. The generators should throw an exception if they see something they don't like. In the future we should have a better way to set generator arguments (something that provides more guidance than a simple text field). It should include validation. Completed verified |