I forgot to mention that this must work for SNAPSHOTs as well, which
confirms this is not something which needs to be resolved with the
maven-release-plugin, but in Maven Core.
Robert
On Mon, 12 Dec 2016 10:16:46 +0100, Tibor Digana <tibordig...@apache.org>
wrote:
Is it really necessary to specify version of parent artifact in
<parent/>?
Suppose we have multimodule reactor project and maven-release-plugin
would
inline the version in the <parent/> section and remove it again in new
development iteration. The plugin fails then if the parent version is not
determined.
WDYT?
If I specify {project.version} in child POM dependencies I do it for the
reason to not to know anything about inconsistent versions. The parent
section with specific version breaks this idea because the parent runs
child and thus child should know the caller.
Maybe groupId+artifactId+relativePath in parent would be enough in such
project.
Cheers
Tibor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
