maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Hoß (JIRA) <>
Subject [jira] Created: (MCHANGES-188) Announcement collides with ${changes.version} property
Date Wed, 02 Dec 2009 11:48:55 GMT
Announcement collides with ${changes.version} property

                 Key: MCHANGES-188
             Project: Maven 2.x Changes Plugin
          Issue Type: Bug
          Components: announcement
    Affects Versions: 2.2
            Reporter: Sebastian Hoß

When you set the ${changes.version} property manually (e.g. to specify the version of the
changes plugin itself) the changes-plugin uses the given value as the projects version and
fails if you don't have a matching release with the exact same version number.

This behavior is AFAIK not documented anywhere and should either be changed or documented.
I stumbled upon this yesterday and wrote an mail with further information and a stack trace
for this here:

The plugins documentation[1] itself says that ${project.version} is the default value for
the version field, however the code[2] tells that version is set to the expression="${changes.version}"
with a default-value="${project.version}". So this "bug" only affects people who have defined
a ${changes.version} property. Changing the name of the property resolves this.

This only affects the announcement goals, jira-report along mvn site runs fine which may be
a little confusing for users who have a running mvn site configuration and now want to add
announcement mails but run into this problem (like myself in this case).


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