RFC-2141 NID compliance

[eedzjee]

According to chapter 2.1 in the RFC-2141, the NID can contain up to 32 characters, numbers and hyphens. With the first character not to be a hyphen: https://www.ietf.org/rfc/rfc2141.txt

I've fixed this in the URN.java class and added tests for them. I tried to fix all qulice warnings, but couldn't comply with the 'AbbreviationAsWordInNameCheck' of the URN class itself as it would break the library's compliancy.

Also some dependencies could be updated in the parents as they haven't been changed in a while.

[0crat]

@yegor256/z everybody who has role REV is banned at #20; 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)

[eedzjee]

I fixed the build, but was unable to suppress the Checkstyle warnings about 'AbbreviationAsWordInNameCheck':

Checkstyle: C:\projects\jcabi-urn\src\main\java\com\jcabi\urn\URN.java[69]: Abbreviation in name 'URN' must contain no more than '2' consecutive capital letters. (AbbreviationAsWordInNameCheck)
[INFO] Checkstyle: C:\projects\jcabi-urn\src\main\java\com\jcabi\urn\URN.java[233]: Abbreviation in name 'toURI' must contain no more than '2' consecutive capital letters. (AbbreviationAsWordInNameCheck)

Do you know how to do this @yegor256 ? Adding @SuppressWarnings("checkstyle:abbreviationaswordinname") doesn't seem to help.

[eedzjee]

assign @yegor256

[0crat]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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]

@yegor256/z everybody who has role REV is banned at #20; 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)