Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checkstyle will fail in HeaderCheck if header contains a a letter with acute sign #1045

Open
fabriciofx opened this issue May 3, 2019 · 15 comments

Comments

@fabriciofx
Copy link

fabriciofx commented May 3, 2019

I'm using qulice version 0.18.17 and Checkstyle fails if I'm using a letter with acute sign at header (HeaderCheck):

Checkstyle: C:\Users\fbc\workspace\fabriciofx\cactoos-jdbc\src\main\java\com\github\fabriciofx\cactoos\jdbc\package-info.java[4]: Line does not match expected header line of ' * Copyright (c) 2018 Fabrício Barros Cabral'. (HeaderCheck)

The LICENCE.txt file has the same string.

@0crat
Copy link
Collaborator

0crat commented May 3, 2019

@krzyk/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented May 3, 2019

@fabriciofx/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@fabriciofx fabriciofx changed the title Checkstyle will fail in HeaderCheck if header contains a a letter with acute signal Checkstyle will fail in HeaderCheck if header contains a a letter with acute sign May 3, 2019
@fabriciofx
Copy link
Author

@krzyk ping

@krzyk
Copy link
Collaborator

krzyk commented Jun 27, 2019

@0crat in

@0crat 0crat added the scope label Jun 27, 2019
@0crat
Copy link
Collaborator

0crat commented Jun 27, 2019

@0crat in (here)

@krzyk Job #1045 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jun 27, 2019

Bug was reported, see §29: +15 point(s) just awarded to @fabriciofx/z

@0crat
Copy link
Collaborator

0crat commented Jun 27, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 2, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 7, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 12, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 17, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 22, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Jul 27, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 1, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 6, 2019

@krzyk/z everybody who has role DEV is banned at #1045; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256 yegor256 removed the scope label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants