Is your feature request related to a problem? Please describe.
Maven 4 publishes consumer and build poms for a given project. Build poms are a verbatim copy of the source pom.xml and thus they do not evaluate their properties. This causes pomchecker to trigger in some cases.

Describe the solution you'd like
Skip processing build poms with pomchecker. Maven Central applies laxer rules to this kind of files at the moment.

Describe alternatives you've considered
Either removing build poms from publication or manually editing them before remote staging.

Additional context
#1631