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

Shmakov Alexey updated CAMEL-19114:
-----------------------------------
    Description: 
```
File "buildingtools\src\main\resources\camel-checkstyle-suppressions.xml" 
contains list of style check supressions
The path mask ("file" field) for supressions is based on the Java regex pattern 
and for platform-independent processing it is required to write path separators 
as '[\\\/]', not '/'. Now, in the part of the supressions in this file, the 
separators are written as needed '[\\\/]', and in the part - as in Linux '/'. 
As a result, style check fails for Windows OS.
```

  was:
File "buildingtools\src\main\resources\camel-checkstyle-suppressions.xml" 
contains list of style check supressions
The path mask ("file" field) for supressions is based on the Java regex pattern 
and for platform-independent processing it is required to write path separators 
as '[\\\/]', not '/'. Now, in the part of the supressions in this file, the 
separators are written as needed '[\\\/]', and in the part - as in Linux '/'. 
As a result, style check fails for Windows OS.


> Repair check-style for Windows OS
> ---------------------------------
>
>                 Key: CAMEL-19114
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19114
>             Project: Camel
>          Issue Type: Bug
>          Components: build system
>            Reporter: Shmakov Alexey
>            Priority: Major
>
> ```
> File "buildingtools\src\main\resources\camel-checkstyle-suppressions.xml" 
> contains list of style check supressions
> The path mask ("file" field) for supressions is based on the Java regex 
> pattern and for platform-independent processing it is required to write path 
> separators as '[\\\/]', not '/'. Now, in the part of the supressions in this 
> file, the separators are written as needed '[\\\/]', and in the part - as in 
> Linux '/'. As a result, style check fails for Windows OS.
> ```



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to