bogus relativePath's after git migration

I noticed that after git migration we got a few "skewed" relativePath references.

Without relativePath then its hard/tricky to test changes in parent pom without having to mvn install it for every change, and the build will also fail if without network access - thus I suggest we get these fixed.

I think my patches are clean but i'll just for good measure open a pullrequest for the ones with more than just a simple change in the root pom.xml.