[
https://issues.jboss.org/browse/FORGE-2202?page=com.atlassian.jira.plugin...
]
George Gastaldi closed FORGE-2202.
----------------------------------
Fix Version/s: 2.14.0.Final
(was: 2.x Future)
Resolution: Done
Feature implemented.
Created command {{Java: Set Default Formatter}} to specify the formatter XML to be used.
This information will be stored in the {{~/.forge/config.xml}} file. After that, every
call to JavaResource.setContents() will format the sources before persisting.
An improvement to this issue is to store the formatter path/name in the Project's
configuration thru {{ConfigurationFacet}}.
Provide formatter configuration when using Forge
------------------------------------------------
Key: FORGE-2202
URL:
https://issues.jboss.org/browse/FORGE-2202
Project: Forge
Issue Type: Feature Request
Components: Builtin Plugins, Configuration, Parsers / File Manipulation
Affects Versions: 2.x Future
Reporter: Ivan St. Ivanov
Assignee: George Gastaldi
Fix For: 2.14.0.Final
When Forge generates code it formats it with the current Forge [Eclipse-based] formatter:
3 spaces indentation and opening braces on the next line. As mentioned by George in the
mailing list, if you develop an addon, it is possible to control that via the Roaster API
by calling Roaster.format() passing as an argument the Eclipse formatter profile XML.
However, it would be a good idea if I am just a Forge user to be able to configure the
already existing addons that generate code (e.g. the new entity command) to use a
formatter that I have provided, so that the generated code follows the code conventions
adopted in the project/team I work in
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)