Lee Meador wrote:
This does not work.
If you think about it you can see why.
You would define 'sensage-version' in the parent pom and use it in all
the
children. The problem is that as it is parsing the child pom, maven
has to
find the parent. To do that, it looks in the <parent> section and has
to use
the value of "sensage-version'.
Not really, since I pass in the value of sensage-version via a -D flag.
Maven just refuses to resolve it within a <parent>...</parent> section.
Its a classic catch-22 situation. You can't find the parent without the
value of 'sensage-version' and you you can't find the value of
'sensage-versin' without the parent.
Yeah, I guess so... I'm wondering, though, why maven can't just go look
in the parent directory for a pom.xml file and not require me to specify
where the parent is - after all, maven has no qualms about imposing all
sorts of directory structure conventions, so why not just go that extra
step, or at least have a tag "use whatever is in the parent directory"....
Meanwhile, I guess I just need to live with having to manage all
versions in all the pom.xml files by hand - sigh -.
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
