By now I do not plan to publish to maven central.
But if I find the time to learn how to do it, maybe in some future.
Also I am quite sure that I won't get a plausible PGP key for net.sourceforge, which maven central requires for publishing.
I guess therefore I would have to change the packagename "net.sourcforge.barbecue" to something else.
Last edit: HuDeanY 2024-03-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I integrated your proposed patch.
See barbecue-2.0 tag.
Fixed lots of code warnings also.
Test look good.
great thanks. Will the 2.0 tag be published to maven central?
By now I do not plan to publish to maven central.
But if I find the time to learn how to do it, maybe in some future.
Also I am quite sure that I won't get a plausible PGP key for net.sourceforge, which maven central requires for publishing.
I guess therefore I would have to change the packagename "net.sourcforge.barbecue" to something else.
Last edit: HuDeanY 2024-03-01