[forge-issues] [JBoss JIRA] (ROASTER-126) Format options not taken into account

[Luca Burgazzoli (JIRA)]

    [ https://issues.jboss.org/browse/ROASTER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420987#comment-13420987 ] 

Luca Burgazzoli commented on ROASTER-126:
-----------------------------------------

As I set the FORMATTER_LINE_SPLIT to 120, should't the code split at the 120th char ? 
As far as I can see now it splits at the 80th.

> Format options not taken into account
> -------------------------------------
>
>                 Key: ROASTER-126
>                 URL: https://issues.jboss.org/browse/ROASTER-126
>             Project: Roaster
>          Issue Type: Bug
>          Components: Formatter
>    Affects Versions: 2.20.0.Final
>            Reporter: Luca Burgazzoli
>            Priority: Minor
>
> I'm doing some small experiments with Forge Roaster and I'm unable to get some formatting options taken into account.
> My code and the result is here: https://gist.github.com/lburgazzoli/115377c3887972696f77db3a71fef85f
> As you can notice, I configured some properties so that the code should wrap at column 120 and it should use spaces instead of tabs but my set-up is ignored and the resulting code is still formatted with some defaults.
> I set the formatting properties with:
> {code:java}
>     properties.put(DefaultCodeFormatterConstants.FORMATTER_LINE_SPLIT, "120")
>     properties.put(DefaultCodeFormatterConstants.FORMATTER_TAB_CHAR, "space")
>     properties.put(DefaultCodeFormatterConstants.FORMATTER_TAB_SIZE, "4")
> {code}
> The behaviour does not change if I use constants without the shaded package value.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)