I think this is a good idea. And I'd go one step further and use
"versionless" <dependency> to represent in-reactor version.
--
Regards,
Igor
On December 12, 2016 1:16:49 AM 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
