accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-957) Modify codestyle formatter to allow turning off the formatter
Date Fri, 11 Jan 2013 19:08:13 GMT


Christopher Tubbs commented on ACCUMULO-957:

I don't think this is IDE specific markup. It's just a comment to turn any formatter on/off.
(We can actually use a different syntax if we want... the formatter will respect any string.
@formater:on and @formater:off are only the default such strings). Regardless, it has the
same semantic meaning, even to a human "formatter", of "please don't change the formatting
of this section; I put it this way for a reason", regardless of the IDE features you are using.
> Modify codestyle formatter to allow turning off the formatter
> -------------------------------------------------------------
>                 Key: ACCUMULO-957
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Trivial
>             Fix For: 1.5.0
>   Original Estimate: 1m
>  Remaining Estimate: 1m
> The setting, "org.eclipse.jdt.core.formatter.use_on_off_tags" should be set to value
"true" in the codestyle xml file for Eclipse.
> This enables overriding the formatter for specific blocks where the automatic formatter
doesn't produce easy to read code. This should be used sparingly, so it doesn't allow constant
circumvention of established standards.
> {noformat}
> <setting id="org.eclipse.jdt.core.formatter.use_on_off_tags" value="true"/>
> {noformat}
> allows
> {code:java}
>   /* @formatter:off */
>     int a=1, // formatter
>         b=2, // is
>         c=3, // off
>         d=4; // for now
>   /* @formatter:on */
> {code}
> The above is not a good example, but it demonstrates what this ticket is about. It would
require users to update their codestyle settings in Eclipse.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message