for the vnu.jar releases, that one gets automatically bumped
anyway, the version numbers are hardcoded into the
./build/build.py file
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.
OK, I will try to get new Maven packages released this weekend or early next week
and I am not sure when I can make time
@boris-petrov: if that’s what would work for you, yes
as far as I can see, whatever code you’ve written now would work exactly the same with the fat jar — the API doesn’t change
I guess there might be some Maven problem due to the fat jar including some dependencies that you already have installed through Maven
but I don’t know, because I’ve never actually ever used Maven myself
I guess there might be some Maven problem due to the fat jar including some dependencies that you already have installed through Maven
Yes, that's the problem I have. And also the fact that this fat-jar is updated all the time and I can't set a specific version (for example if the new one has some bug or introduces a check I can't fix right away or something). And that's why the Maven artifacts are nice. But isn't the process for releasing the fat-jar similar to the one for Maven Central? I also see there is an artifact in GitHub packages - https://github.com/validator/validator/packages/892686 - I could in theory use that one (I guess it's the same as in Maven Central) - so perhaps you could at least keep this one up-to-date?
what I mean is, it’s not sufficient for me to update just the validator maven package itself, but also need to update any of the dependencies that have changes
at this point, the two that have significant changes are the css-validator package, and the htmlparser package
however, creating the packages for those is a lot less time-consuming than doing the validator package
for the validator package — or really, any new major release of the validator itself — I need to complete the changelog and the “what’s new” documentation
and since it’s been more than a year since the previous major release, that leaves me with quite a bit of stuff to try to summarize in those docs
doing that is really what takes up the majority of the time needed to prepare a release
I agree, keeping a changelog is kind of tiresome. You could link to the specific changelogs (if there are such) of the sub-packages themselves and in the validator package just say "css-validator was updated (here's its changelog)". Another thing you could do is use an automated tool to create a changelog from the commits. A third way would be to just say "multiple changes and fixes, please check the commits" and be done with it. :D In any case having new releases is much more important than having a changelog. I guess most people would agree that we prefer having new versions with all the latest fixes every couple of months without a changelog instead of not having new versions. :)
In any case - if you're really sure you won't have the time to create a new release now (and/or in the future) I guess I'll have to just use the fat-jar as an external tool to my app.
how I allow validate my localhost ?