Subject
How to avoid hardcoding
parent pom version in
Hi Farrukh,
The version for the pom is required, so you can't remove that
from the child poms. Usually, you only change the version of your
project when you release it. The maven release plugin already updates
all the versions of the parent and child poms (in trunk) when it tags
the release
Farrukh,
Use the on your parent pom where you specify the
version for a given plugin, then your child poms will inherit the version
number.If you need to upgrade to a higher release, you simply have to
change one pom file.
Here's an example:
Parent pom:
If you use the release plugin, the change will be done automatically.
Arnaud
On 20/08/07, Farrukh Najmi <[EMAIL PROTECTED]> wrote:
> I have a fairly large multi-project maven 2 project. All my child
> projects specify parent poms version using something like:
>
>
> myid
> a.b
I have a fairly large multi-project maven 2 project. All my child
projects specify parent poms version using something like:
myid
a.b.c
parent-pom-version
Every time I change parent pom's version I have to update all the child
poms.
How can I avoid hardcoding the
