Maven Changelog Plugin
  1. Maven Changelog Plugin
  2. MCHANGELOG-125

Support regexp capturing group in issueIDRegexPattern configuration property

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Auto Closed
    • Affects Version/s: 2.3
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Any

      Description

      In order to support more complex issue id detection in changelog comments, I propose to support regexp capturing group in <issueIDRegexPattern /> configuration property.

      For example, with a Trac Issues Management System, I use
      <issueIDRegexPattern>#(\d+)</issueIDRegexPattern>
      <issueLinkUrl>http://trac.host/path/to/trac/project/ticket/%ISSUE%</issueLinkUrl>
      and the %ISSUE% keyword will be replaced by the issue number (without the prefixing '#')

      I have successfully tested a simple modification of ChangeLogReport.java / sinkIssueLink() / line: 1319
      replace:
      String match = matcher.group();
      by:
      String match;
      if(matcher.groupCount() == 1)

      { match = matcher.group(1); }

      else

      { match = matcher.group(); }

      Hope this little modification can be adopted and put in 2.3 release.

      Best regards.

      Eric

        Activity

        Hide
        Markus Spann added a comment -

        I'm totally with Eric on this issue. A single capturing group as described would be most helpful.
        Our tickets are incrementing integers. The regex \d

        {2,}

        is really too fuzzy.

        Show
        Markus Spann added a comment - I'm totally with Eric on this issue. A single capturing group as described would be most helpful. Our tickets are incrementing integers. The regex \d {2,} is really too fuzzy.
        Hide
        Michael Osipov added a comment -

        This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

        Show
        Michael Osipov added a comment - This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Blanchard
          • Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development