This is a known issue. We have:
- an open JIRA for automatic parent versioning in Maven 2.1 to remove
the need for this altogether
- I'm aware that there is an issue with not writing in environment
specific properties on deployment as we should, but I'm not sure if
this is in JIRA.
You can use the release plugin to ease the burden of parent version management.
- Brett
On 4/28/06, LaCasse, John <[EMAIL PROTECTED]> wrote:
When I do an install of a pom that has a parent where the parent version
element is specified via a property, the property isn't being expanded
in the generated installed or deployed pom.
Eg:
<parent>
...
<version>${env.version}</version>
</parent>
In the generated installed pom it is still specified as ${env.version}
instead of the expanded value.
At least in the version case, this is quite undesirable. And having to
edit every pom and hard code a new version for every build would not be
very pleasant as well as error prone (at least for a project with many
sub projects as I have). Any suggestions are appreciated?
Thanks,
Jpl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
