[ 
https://issues.apache.org/jira/browse/FLUME-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lior Zeno updated FLUME-2949:
-----------------------------
    Description: 
Now that style violations fail Flume build process, Flume fails to build on 
Windows.
The reason for that is that file paths in checkstyle-suppresions.xml are 
written with non-portable separators. Switching to "[/\\]" as a path separator, 
should fix this issue.
References: 
* http://checkstyle.sourceforge.net/config_filters.html#SuppressionFilter
* 
http://checkstyle.2069334.n4.nabble.com/suppression-filter-regex-td2070198.html

  was:
Now that style violations fail Flume build process, Flume fails to build in 
Windows.
The reason for that is that file paths in checkstyle-suppresions.xml are 
written with non-portable separators. Switching to "[/\\]" as a path separator, 
should fix this issue.
References: 
* http://checkstyle.sourceforge.net/config_filters.html#SuppressionFilter
* 
http://checkstyle.2069334.n4.nabble.com/suppression-filter-regex-td2070198.html

        Summary: Flume fails to build on Windows  (was: Flume fails to build in 
Windows)

> Flume fails to build on Windows
> -------------------------------
>
>                 Key: FLUME-2949
>                 URL: https://issues.apache.org/jira/browse/FLUME-2949
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: v1.7.0
>            Reporter: Lior Zeno
>             Fix For: v1.7.0
>
>         Attachments: FLUME-2949-0.patch
>
>
> Now that style violations fail Flume build process, Flume fails to build on 
> Windows.
> The reason for that is that file paths in checkstyle-suppresions.xml are 
> written with non-portable separators. Switching to "[/\\]" as a path 
> separator, should fix this issue.
> References: 
> * http://checkstyle.sourceforge.net/config_filters.html#SuppressionFilter
> * 
> http://checkstyle.2069334.n4.nabble.com/suppression-filter-regex-td2070198.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to