>> -- how about excluding the docbook module from the Maven deploy - it does >> not contain any artifacts other than the POM > Good idea in my opinion. I suppose the indented way is to remove the > module in the top-level pom?
I believe removing the module is not an option, because that takes it completely out of the release too - no more updates to the version in that module then. I would suggest adding a property setting "maven.deploy.skip" to "false" within the POM of that module or adding a plugin configuration section for the Maven deploy plugin settings the "skip" parameter to "false". -- Richard
