Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: 1.6
    • Labels:
      None
    • Environment:
    • Number of attachments :
      0

      Description

      Allow entries to be sorted by action type.

      Today, I must sort (and keep sorted the action entries in changes.xml. It would be nice to be able to specify - perhaps in the properties file - that the generated XML and text file be sorted by action. Maybe something like:

      maven.changes.action.sort = add, fix, update, remove

        Activity

        Hide
        Vincent Massol added a comment -

        Hi Gary,

        Could you please provide more information as to why this is required?

        Also, you mention some generated XML/text but AFAIK there's no generation of any file (apart from the HTML one) in the changes plugin. Could you please explain more?

        Thanks

        Show
        Vincent Massol added a comment - Hi Gary, Could you please provide more information as to why this is required? Also, you mention some generated XML/text but AFAIK there's no generation of any file (apart from the HTML one) in the changes plugin. Could you please explain more? Thanks
        Hide
        Gary Gregory added a comment -

        Correct, changes.xml produces HTML. I was also thinking of the annoucement plugin.

        Here is what I have in mind: when I read the (very nice BTW) HTML history report, I'd like to read things in groups. Here are all of the new features for this release first (the most important IMO). Then maybe I want to know what all of the bug fixes are, then all of the updated pieces and last all of the pieces that have been deprecated.

        Today I have to do all of this by hand in changes.xml, which is a pain. It is also possible that someday, we'll have a clever plugin that can create a changes.xml from Bugzilla or Jira, and who knows what the order of things in the file will be.

        It would be nice to be able to specify some UI view parameters separately from what I think of as the data model in changes.xml. Which is why I proposed to parameterize this in the proerties file.

        Now that I think of it, another tweak would be the option to have a header that says "New Features" and "Bug Fixes" just like there is a header today for the Release number and date.

        Show
        Gary Gregory added a comment - Correct, changes.xml produces HTML. I was also thinking of the annoucement plugin. Here is what I have in mind: when I read the (very nice BTW) HTML history report, I'd like to read things in groups. Here are all of the new features for this release first (the most important IMO). Then maybe I want to know what all of the bug fixes are, then all of the updated pieces and last all of the pieces that have been deprecated. Today I have to do all of this by hand in changes.xml, which is a pain. It is also possible that someday, we'll have a clever plugin that can create a changes.xml from Bugzilla or Jira, and who knows what the order of things in the file will be. It would be nice to be able to specify some UI view parameters separately from what I think of as the data model in changes.xml. Which is why I proposed to parameterize this in the proerties file. Now that I think of it, another tweak would be the option to have a header that says "New Features" and "Bug Fixes" just like there is a header today for the Release number and date.
        Hide
        Vincent Massol added a comment -

        ok, I understand now. I have implemented a first version of it.

        Show
        Vincent Massol added a comment - ok, I understand now. I have implemented a first version of it.

          People

          • Assignee:
            Vincent Massol
            Reporter:
            Gary Gregory
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: