You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jens Riboe <jr...@wilytech.com> on 2006/08/03 13:04:32 UTC

[M2] Application version in multi-module project

Background:
I have a typical multi-module project, with a parent pom and a handful
of child poms inheriting from the parent.

The parent pom contains the version, which is inherited to the child
poms, which affect all generated child artifacts. So far so good.

Problem:
However, the parent pom is referred by version from each child pom,
which causes a slight maintenance problem when it's time to change the
version number. 

I have to update the version number in the parent pom, as well as all
references to the parent in each child pom. Clearly, this is clumsy.

AFAIK the version number of the parent must be present in the child pom.

Question:
So, what are the best practices for this problem?

Bi-condition:
I'm working mostly off-line, so the release plug-in is not appropriate
in my case.

Many thanks in advance for any tips,
	/Jens


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org