[
https://issues.jboss.org/browse/ROASTER-131?page=com.atlassian.jira.plugi...
]
Gunnar Morling edited comment on ROASTER-131 at 1/21/19 6:55 AM:
-----------------------------------------------------------------
Hey [~gastaldi], I'm not totally sure what's the implication of
{quote}
(at least you get some default values that can be overriden by the configuration file).
{quote}
In any case, it should not be the expectation that the
"org.eclipse.jdt.core.compiler.source" option is part of the XML configuration
file. When exporting that file from the IDE, this option will not be contained. So if
someone had added it manually before, it will easily be missed when updating the file with
a newly exported one.
was (Author: gunnar.morling):
Hey [~gastaldi], I'm not totally sure what's the implication of
{quote}
(at least you get some default values that can be overriden by the configuration file).
{quote}
In any case, it should not be the expectation that the
"org.eclipse.jdt.core.compiler.source" option is part of the XML configuration
file. When exporting that file from the IDE, this option will not be contained. So if
someone had added it manually, it will easily be missed when updating the file with a
newly exported one.
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
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)