Did you find a solution? I'm noticing the same problem.
The POM version is changed from 1.0.0.1-SNAPSHOT to 1.0.0.1 for the release,
and then up to 1.0.0.2-SNAPSHOT for the next development.
But the internal project dependencies are not changed from 1.0.0.1 to
1.0.0.2-SNAPSHOT. It seems like a definite bug, unless I'm missing
something in the way that the POM was supposed to be written.
Harold
Markku Saarela wrote:
>
> Hi,
>
> After release:perform snapshot version project pom.xml include
> dependency versions for dependent projects remains to new release
> version ex. 1.0a not new development version ex 1.0-SNAPSHOT. I couldn't
> find anything from google concerning this issue. Is there any way to
> avoid this. It's annoying because there are over 40 modules in project.
>
> Regards, Markku Saarela
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/M2-release-plugin-snapshot-version-does-not-handle-new-development-depency-version-correctly-in-multimodule-project-tf2152810.html#a6575828
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
