Operating System: All
Platform: All

Tomas,

Could you please add a little more detail to this.

Here is what I am looking for.

a. What is wrong?
b. Where is it wrong? A list of projects where the pom needs to be cleaned up would be useful.
c. What is the right thing to do? Use plugin management maybe. If you have examples of how to do it right that would be great.

Moiz,
There are dependencies with versions that override parent pom's dependencyManagement.
e.g.
echo -e 'setns a=http://maven.apache.org/POM/4.0.0\nxpath //a:dependency[descendant::a:version]/a:artifactId/text()' | xmllint --shell ./topology-lldp-discovery/pom.xml
/ > setns a=http://maven.apache.org/POM/4.0.0
/ > xpath //a:dependency[descendant::a:version]/a:artifactId/text()
Object is a Node Set :
Set contains 1 nodes:
1 TEXT
content=commons-lang

I also saw guava and other lib versions hardcoded. Actually the pom above is even more broken - it should use org.apache.commons:commons-lang3 as defined in commons.

Regarding plugins, yang-maven-plugin is configured on multiple places. It should be moved do a parent pom, same way as it is in config subsystem.

Master have cleaned up pom files as of now.