[
https://issues.apache.org/jira/browse/ACCUMULO-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562942#comment-13562942
]
Hudson commented on ACCUMULO-957:
---------------------------------
Integrated in Accumulo-Trunk-Hadoop-2.0 #28 (See
[https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/28/])
ACCUMULO-957 Enable turning formatter on/off for special use cases. Remove
comment from overriding methods, and make LICENSE header comment a regular
comment. (Revision 1438630)
Result = SUCCESS
ctubbsii :
Files :
* /accumulo/trunk/contrib/Eclipse-Accumulo-Codestyle.xml
* /accumulo/trunk/contrib/Eclipse-Accumulo-Template.xml
> Modify codestyle formatter to allow turning off the formatter
> -------------------------------------------------------------
>
> Key: ACCUMULO-957
> URL: https://issues.apache.org/jira/browse/ACCUMULO-957
> 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: http://www.atlassian.com/software/jira
