maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Kossakowski (JIRA)" <>
Subject [jira] Commented: (MNG-2339) ${project.*} are interpreted in the wrong place
Date Sun, 03 Feb 2008 23:42:59 GMT


Grzegorz Kossakowski commented on MNG-2339:

Guys, the situation with this issue is really, really annoying.

The issue is more than one year old, affects so many people that most of them (including me)
sees it as the most ugliest unresolved bug in Maven. I don't know why you require any IT even
if there are many projects (Apache Cocoon, Jetty plug-in, Spring to name a few) that exhibit
behaviour described in this issue.

At Apache Cocoon, we have many poms polluted just because of this issue and our users who
being worried about whole Maven thing are hit by it at the nearly beginning, see:
for latest example. It's not perfect first expierience, don't you think?
Demanding any additional action for such embarrassing bug is just a PITA, IMHO.

Sorry for a little rant but I think it's the time to say: enough is enough.

Devoted Maven user,

> ${project.*} are interpreted in the wrong place
> -----------------------------------------------
>                 Key: MNG-2339
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.4
>            Reporter: Emmanuel Venisse
>            Assignee: Kenney Westerhof
>            Priority: Critical
>             Fix For: 2.0.9
> If a plugin use ${project.version}, this parameter is interpreted with the version of
the current project and not the plugin version. I think we have the same pb with dependencies
and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT, ${project.version}
used in the plugin will be interpreted as 1.0-SNAPSHOT instead of 2.0

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message