Hi Satish, I guess you're adjusting the parent version manually? This doesn't get picked up by the child modules since in the child poms you're still referencing the parent with its old version.
You could always use the release-plugin to release your versions (which is the preferred way to cut a release).. A "release:prepare" will iterate through the modules of a POM project and prompt you for the desired version to set on them (defaults are usually just fine).. Cheers Jo On 2/26/07, Terala, Satish (IS Consultant) <[EMAIL PROTECTED]> wrote:
I believe this problem has already been discussed in the maven community as I see a jira that was opened. I am not quite sure if there is a solution yet. Here is the Jira http://jira.codehaus.org/browse/MNG-521?page=com.atlassian.jira.plugin.s ystem.issuetabpanels:comment-tabpanel#action_42869 Problem : I want to update the version number of my application (ear with multiple jars and wars) at the parent level and propogate it to the children. I update the version element of the parent pom but that only create a new parent pom definition , but the children continue to build with old version. The only way I can force each child project version change is by modifying the version number in the parent element of the child pom's. Given that my parent project has about 10 sub projects (hence poms') what is the correct solution to do this. I tried using the ${project.version} attribute , but that does'nt help since the child pom's only use the version value defined in the parent ' version element of their pom. Thanks -satish
