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.
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. I guess therefore I would have to change the packagename "net.sourcforge.barbecue" to something else.
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.
I integrated your proposed patch. See barbecue-2.0 tag. Fixed lots of code warnings also. Test look good.
Fixed code warnings
Fixed code warnings
Improved pom.xml by ticket #6 patch
Improved pom.xml by ticket #6 patch