Maven Changes Plugin (moved to ASF)
  1. Maven Changes Plugin (moved to ASF)
  2. MCHANGES-240

Support: version="${poject.version}" date="${buildDate}"


    • Type: Bug Bug
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.4
    • Fix Version/s: None
    • Component/s: changes.xml
    • Labels:
    • Number of attachments :


      Currently the plugin requires a release version which is equal to $

      {poject.version} without "-SNAPSHOT".
      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 releasing.

      Consider to provide the property $


      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">



        No changes have yet been made on this issue.


          • Assignee:
            Florian Brunner


            • Created: