It seems like the actual `checkPom` task is only examining `<dependency>` blocks and not any other data. So, on the one hand, the existing behavior was "copy the actual pom to the expected pom" is what's happening, but a developer will then need to examine which difference should actually be added to their commit.
So that's strange and we should decide if `checkPom` should also be checking, for instance, the `<packaging>` for consistency. Or decide that what goes into a diff is just developer responsibility. [ Full content available at: https://github.com/apache/geode/pull/2569 ] This message was relayed via gitbox.apache.org for notifications@geode.apache.org
