Cleanup pom.xml files using dependencymanagement and pluginmanagement in the parent pom.xml file
Also, I encapsulated the distributionmanagement into profiles so that my research groups jenkins server can easily deploy to the internal artifactory server so that I am using my latest copy of sesametools for downstream jenkins builds. The fortytwo.net distributionmanagement profile is active by default so it shouldn't affect your jenkins server.
Cleanup pom.xml files using dependencymanagement and pluginmanagement in the parent pom.xml file
Also, I encapsulated the distributionmanagement into profiles so that my research groups jenkins server can easily deploy to the internal artifactory server so that I am using my latest copy of sesametools for downstream jenkins builds. The fortytwo.net distributionmanagement profile is active by default so it shouldn't affect your jenkins server.