IMHO this solution is very bad because of one reason: It influences already released versions. IMHO mavens "deploy" goal does not put the correct resolved version into the parent tag. Thus all versions you ever deploy will resolut in corrupt poms because they lead to newer parent poms as soon as there is a new release an thus receive a newer version name on themselves.
following scenario: Parent V1.0.0 --> Child V1.0.0 resolves to parent 1.0.0 and uses version 1.0.0 for itself Parent V1.0.1 --> Child V1.0.1 resolves to parent 1.0.1 and uses version 1.0.1 for itself But what happens to original V1.0.0 as soon as the V1.0.1 parent is present in any repository? It will resolv V1.0.1 because this is the newest. And know you have to childs, both of them telling you that they are V1.0.1. No thats really bad. Maybe I am wrong and deploy-goal does more I am knowing of :)
