Ideally build/configuration-properties-collector should NOT use the public parent POM, because that POM includes lots of things that simply don’t make sense for internal modules; the release is only one aspect.

But at the very least, if we really need to use that parent POM, we should take the appropriate steps to make sure this module does not get published to Maven Central when we release Hibernate Search. This probably involves settings some Maven properties or disabling some plugins.