The jar release gets updated/rebuilt every time I push
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
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..
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.
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
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.
Right. I really don't want to take much of your time. The best solution for me would be to get new versions for all the packages on MC. If you can do that in the next few days/weeks, that's great. If not, in any case I will try to create my own packages in a local Maven repo so I can continue using the validator package from my app.