maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] Commented: (MCHANGES-240) Support: version="${poject.version}" date="${buildDate}"
Date Thu, 12 May 2011 20:51:22 GMT


Dennis Lundberg commented on MCHANGES-240:

The process should not be error prone. The current version of the plugin already checks that
the version in changes.xml is in sync with the version in the POM.

Using the changes-check goal you can make sure that a valid date has been entered in the changes.xml

> Support: version="${poject.version}" date="${buildDate}"
> --------------------------------------------------------
>                 Key: MCHANGES-240
>                 URL:
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: changes.xml
>    Affects Versions: 2.4
>            Reporter: Florian Brunner
>            Priority: Critical
> Currently the plugin requires a release version which is equal to ${poject.version} without
> Currently the changes.xml doesn't get filtered.
> The actual version is only known when you do a relase (e.g. using the Maven Release Plugin).
> It's then when you specify if you change e.g. from  version 1.1.2 to 1.1.3 or 1.2.0
> Keeping this in sync with the changes.xml is currently a manual process which has to
be done immediatly before releasing and is thus very error prone (especially if you're releasing
every day or every other day in a hot phase of the project)!
> For this reason
> <release version="${poject.version}"...
> should be supported.
> The same is true for the release date. You only know the exact date, when you're actually
> Consider to provide the property ${buildDate}.
> Provide a hook into the Maven Release Plugin, to add a new release element (after tagging,
when the version gets updated to the next SNAPSHOT version):
>     <release version="${poject.version}" date="${buildDate}" description="Subsequent
>     </release>

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