[
https://issues.jboss.org/browse/ROASTER-131?page=com.atlassian.jira.plugi...
]
Gunnar Morling commented on ROASTER-131:
----------------------------------------
[~gastaldi], tested it and can confirm it works, very nice! About the failure reporting,
tested that, too, and it fails sa expected when enforcing an old language level and using
newer constructs. Any chance though to extract some more context about the exact reason
from the JDT formatter? The current message ("The source cannot be formatted")
is rather generic, so hard to act on it. In any case I'd love a new release based on
the current master, as it will allow me to make Roaster part of my workflow, sharing one
single formatter config between the IDE, Spotless and a shell script for formatting
changed files (might even make that a pre-commit hook). I'm also planning to blog
about this set-up, as it [sparked some
interest|https://twitter.com/gunnarmorling/status/1086265577835032577].
Config file not applied when using CLI
--------------------------------------
Key: ROASTER-131
URL:
https://issues.jboss.org/browse/ROASTER-131
Project: Roaster
Issue Type: Enhancement
Reporter: Gunnar Morling
Assignee: George Gastaldi
Priority: Major
Fix For: 2.20.7.Final, 2.20.8.Final
I'm using the CLI (roaster.sh) to format some source files, but it doesn't apply
the given Eclipse formatter file (passed via -c). As per roaster's output it should
have worked, but clearly it's using a different configuration, e.g. in my XML config
file I'm mandating to only use spaces for indentation, whereas the file is indented
with tabs after roaster ran. Note the config itself can't be the problem, as it's
applied as expected when ran through Spotless.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)