On Sun, Aug 28, 2011 at 2:54 AM, Benson Margulies <[email protected]> wrote:
> On Sat, Aug 27, 2011 at 1:11 PM, Hervé BOUTEMY <[email protected]> wrote:
> The 1.2 POM looks like:
>
> dependencyManagement/dependencies/
> <dependency>
> ...
> <version>${project.version}</version>
> </dependency>
>
> What I think is that it was a BUG that maven actually published this
> pom with the reference to ${project.version}, instead of replacing it
> with 1.2, and so any new release would be better. However, the email
> trail I'm trying to remember was a long time ago, and perhaps the
> answer was that maven is supposed to interpret ${project.version}
> relative to the pom it is sitting in, not the child POM. In which
> case, maven is still busted, and I don't know how to fix this.
I've had some weird stuff happen when I use ${project.version}.
I've been meaning to look into it, but you know what happens...
It would be beneficial for guidance on using this variable.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
