Maven Changes Plugin
  1. Maven Changes Plugin
  2. MCHANGES-240

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

    Details

    • 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:
      None
    • Number of attachments :
      0

      Description

      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 $

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

      </release>

        Activity

        Hide
        Dennis Lundberg added a comment -

        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 file.

        Show
        Dennis Lundberg added a comment - 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 file.
        Hide
        Benson Margulies added a comment -

        Dennis, seems like you don't like this idea at all. Should this JIRA be closed?

        Show
        Benson Margulies added a comment - Dennis, seems like you don't like this idea at all. Should this JIRA be closed?
        Hide
        Dennis Lundberg added a comment -

        I think this issue has merits. There are currently some manual work that needs to be done when using a changes.xml file. It would be nice if it could be more automatic.

        Show
        Dennis Lundberg added a comment - I think this issue has merits. There are currently some manual work that needs to be done when using a changes.xml file. It would be nice if it could be more automatic.

          People

          • Assignee:
            Unassigned
            Reporter:
            Florian Brunner
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: