There are circular dependencies between batik submodules:
batik-svg-dom <-> batik-anim
batik-bridge <-> batik-gvt
batik-bridge <-> batik-script
Since proper maven packaging seems to be almost impossible for the average Java-project, I strongly encourage projects not to try to bee too fancy. Just publish a single module that contains everything, hiding all the hard to avoid circular references between the different packages.