@robertdale, the second occurrence of maven-enforcer-plugin (above) is in the <pluginManagement> section and states plugin's version to be used in every tinkerpop module. Actually, the practice to use plugins and dependencies with different ad-hoc defined versions exists in tinkerpop and I understand the *.version properties like log4j.version defined in this pom as an attempt to unify the versions. The Maven way is to define them in <dependecyManagement> and <pluginManagement> once. Thus, I would suggest a new task - unify the version management of plugins and dependencies the Maven way.
[ Full content available at: https://github.com/apache/tinkerpop/pull/1188 ] This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org
