Tibor Digana 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.
The problem starts when you get the child POM from a repository. And *a*
repository might already be the local one. I.e. your suggestion with the
automated manipluation must happen already at installation/deployment time.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
