Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
sideshowbarker
@sideshowbarker:mozilla.org
[m]
@anwait_gitlab it's not possible to tell the checker to ignore particular files
--filterpattern allows ignoring particular messages
anwait
@anwait_gitlab
k, will purge the folder of the specific file before the validation, thanks @sideshowbarker:mozilla.org
Boris Petrov
@boris-petrov
Hi all, I'm trying to use the CSS validator but I'm getting a lot more (bogus) errors than when using the online version. Perhaps because the latest release is from more than one year ago. I'm getting things like Forbidden code point U+0080., Unknown pseudo-element or pseudo-class “::file-selector-button”. (this one is from Bootstrap 5's CSS), “color”: Invalid RGB function. (when used with var) and so on. What can I do? Are there SNAPSHOT releases for newer builds?
sideshowbarker
@sideshowbarker:mozilla.org
[m]
There's a new release
...if you mean the jar releases
Boris Petrov
@boris-petrov
Where?
I mean the JAR ones, yes.
Boris Petrov
@boris-petrov
Ah, I see. I'm using it via the nu.validator:validator package.
Which doesn't have a new release. I can use directly the css-validator one?
sideshowbarker
@sideshowbarker:mozilla.org
[m]
Yeah
Or the HTML checker validator jar too
Boris Petrov
@boris-petrov
I se that nu.validator:validator depends on nu.validator:cssvalidator. Is this the same package as the one you gave me a link to?
Oh, there's a latest thing...
sideshowbarker
@sideshowbarker:mozilla.org
[m]
That can check both HTML and CSS files, as well as SVG files
Boris Petrov
@boris-petrov
Yes, I'm using this one, but the "stable" release.
Using it from Gradle.
Not sure how to use this "latest" from Gradle. Any ideas?
sideshowbarker
@sideshowbarker:mozilla.org
[m]
Yeah I have no idea where the Gradle packages come from
Not from me
Oh, so they come from Maven?
Boris Petrov
@boris-petrov
Yes.
nu.validator:validator:20.7.2 just means get that package version from Maven.
Or from whatever repository is set.
But "latest" is not on Maven Central I believe?
sideshowbarker
@sideshowbarker:mozilla.org
[m]
Yeah I haven't released a new Maven package since then
Boris Petrov
@boris-petrov
Would you kindly? :D
sideshowbarker
@sideshowbarker:mozilla.org
[m]
Not this week or next, no
So I recommend using the jar releases in the meantime
Boris Petrov
@boris-petrov
The jar release == the link to GitHub releases?
1 reply
sideshowbarker
@sideshowbarker:mozilla.org
[m]
I don't personally understand the use case for the Maven packages unless you are doing some integration into another java app
Boris Petrov
@boris-petrov
That's what I'm doing. But what other case is there for the JAR release?
2 replies
sideshowbarker
@sideshowbarker:mozilla.org
[m]
The jar release gets updated/rebuilt every time I push
Boris Petrov
@boris-petrov
I see... well, it's generally not nice for an application to depend on an artifact that changes every so often and one cannot pin the exact version they need.
That's why it's nice to have Maven Central releases.
In any case, thanks for the info. Please do a Maven Central release when you have the time
Boris Petrov
@boris-petrov
hm, I see that this vnu.jar is a fat-jar so it contains a bunch of classes that I don't want - for example org/slf4j/impl/StaticLoggerBinder.class. Because of it I get SLF4J: Class path contains multiple SLF4J bindings..
1 reply
Boris Petrov
@boris-petrov
Is there at least a way to locally build a maven bundle? ./checker.py bundle seems to do that but only for the "validator" package and not for the rest - cssvalidator, htmlparser, etc.
2 replies
sideshowbarker
@sideshowbarker:mozilla.org
[m]
wait, I have them already
./checker.py cssvalidator-bundle, for example
I am not sure I know how to fix that — that version issue
The thing is, I don’t use the Maven packages myself. At all.
I provide them because some people asked for them
and I spent a huge amount of time writing up a the build code for them
…which by the way I fully realize is idiosyncratic build code, and the “right” way to do it all would be directly with mvn and whatever
Boris Petrov
@boris-petrov
I see. Well, if you remember how you did the releases last time, you could just do the same for a new release. I'm not sure where version numbers come from, for example. I just built the "master" css-validator package and it still has 1.0.8 which is the version in MC.
sideshowbarker
@sideshowbarker:mozilla.org
[m]
I think the version numbers are static ones that I bump myself
the dependency ones are not generated numbers or automatically bumped