You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/03/01 07:30:18 UTC
[jira] [Commented] (YETUS-37) make test-patch ruby-lint plugin
configurable
[ https://issues.apache.org/jira/browse/YETUS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173305#comment-15173305 ]
Sean Busbey commented on YETUS-37:
----------------------------------
ruby-lint will already respect "${PWD}/ruby-lint.yml" ([ref|http://code.yorickpeterse.com/ruby-lint/latest/file.configuration.html#file-locations])
Additionally, it takes {{--config}} with a path:
{code}
busbey2-MBA:yetus busbey$ ruby-lint --help 2>/dev/null | grep "configuration file"
When this command is executed it will try to load a configuration file in
Only the first existing configuration file is loaded.
These configuration files can be used for specifying the presenter, reporting
-c, --config Path to a custom configuration file
{code}
> make test-patch ruby-lint plugin configurable
> ---------------------------------------------
>
> Key: YETUS-37
> URL: https://issues.apache.org/jira/browse/YETUS-37
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Kengo Seki
>
> As with HADOOP-12286, it must be useful if users can change the rules about indentation, naming convention, max line length, enabling/disabling some checks, etc. as suitable for their project's personality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)