Derby
  1. Derby
  2. DERBY-6043

Make JQL default query mode for 'ant genrelnotes'

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10.1.1
    • Fix Version/s: 10.10.1.1
    • Component/s: Build tools
    • Labels:
      None

      Description

      The ant target genrelnotes (from tools/release/build.xml) should use JQL querying mode by default, such that you don't have to specify jira.filter.id when invoking it.

      It will still be possible to specify jira.filter.id to instruct the tool to use an existing JIRA filter if that is required for some reason.

        Activity

        Hide
        Kristian Waagan added a comment -

        I updated the description at http://wiki.apache.org/db-derby/ReleaseNoteProcess .
        Closing issue.

        Show
        Kristian Waagan added a comment - I updated the description at http://wiki.apache.org/db-derby/ReleaseNoteProcess . Closing issue.
        Hide
        Kristian Waagan added a comment -

        Thanks, Rick.

        You can do this behind a firewall, but then you have to instruct ant to use a proxy. Maybe -autoproxy works for you, but it didn't on my system. I had to specify -Dhttp[s].proxyHost and -Dhttp[s].proxyPort. You can put these properties in ANT_OPTS and they will be picked up automatically.
        Note that the first part of the ant target uses HTTP, whereas the last part (fetching the release notes) uses HTTPS. This means you have to specify a proxy for both protocols.

        Committed to trunk with revision 1434599.

        Show
        Kristian Waagan added a comment - Thanks, Rick. You can do this behind a firewall, but then you have to instruct ant to use a proxy. Maybe -autoproxy works for you, but it didn't on my system. I had to specify -Dhttp [s] .proxyHost and -Dhttp [s] .proxyPort. You can put these properties in ANT_OPTS and they will be picked up automatically. Note that the first part of the ant target uses HTTP, whereas the last part (fetching the release notes) uses HTTPS. This means you have to specify a proxy for both protocols. Committed to trunk with revision 1434599.
        Hide
        Rick Hillegas added a comment -

        Thanks, Kristian. The patch looks good to me. I applied it and successfully built 10.10.0.0 release notes. I had to get off my company's VPN to do this and I had to adjust the previousReleaseID in releaseSummary.xml. A cursory check of the release notes indicated that the correct set of issues was identified: issues fixed in 10.10.0.0 but not in the previous 10.9.1.0 release. +1

        Show
        Rick Hillegas added a comment - Thanks, Kristian. The patch looks good to me. I applied it and successfully built 10.10.0.0 release notes. I had to get off my company's VPN to do this and I had to adjust the previousReleaseID in releaseSummary.xml. A cursory check of the release notes indicated that the correct set of issues was identified: issues fixed in 10.10.0.0 but not in the previous 10.9.1.0 release. +1
        Hide
        Kristian Waagan added a comment -

        Attaching patch 1a, which makes JQL the default querying mode for obtaining the list of issues from JIRA.
        Also removes some unnecessary code dealing with the reportDisqualifications property.

        I tested the ant target manually.

        Patch ready for review.

        Show
        Kristian Waagan added a comment - Attaching patch 1a, which makes JQL the default querying mode for obtaining the list of issues from JIRA. Also removes some unnecessary code dealing with the reportDisqualifications property. I tested the ant target manually. Patch ready for review.

          People

          • Assignee:
            Kristian Waagan
            Reporter:
            Kristian Waagan
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development