[ https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4857:
-----------------------------------
Attachment: derby-4857-2a-jirasoap_maven_client.diff
derby-4857-2a-jirasoap_maven_client.stat
Thanks a lot for the feedback, Rick.
I have decided to split the work into three pieces:
a) client code
b) changes to existing ReleaseNotesGenerator
c) ant integration
I have attached patch 2a to add the new client code, and based on the feedback from Rick I
think it is useful enough to be committed right away. Committed to trunk with revision 1027056.
I made some changes compared to patch 1a, most of them were formatting, documentation and
naming changes. Specifically, Rick's comments:
o renamed class to FilteredIssueLister, which is the primary functionality
o made the tool quieter (use reportDisqualifiedIssues=true to make it chattier again)
o added some extra (unused) dependencies to remove the warning message
o (the sanity check will be addressed in the next patch since it lives in ReleaseNotesGenerator)
o I have not done anything more regarding the release id specification
In addition I made the tool always write the data file as UTF-8.
Regarding the ancestry chain, the tool seems to do the right thing as long as it has a release
date for the release being made. Unfortunately, the tool won't have that for new releases...
I will write some test code and investigate further.
For now I have made it possible to override the ancestry chain manually.
> Utilize the SOAP API to fetch JIRA issue list for release notes generation
> --------------------------------------------------------------------------
>
> Key: DERBY-4857
> URL: https://issues.apache.org/jira/browse/DERBY-4857
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.7.1.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-4857-1a-jirasoap_relnotes.diff, derby-4857-1a-jirasoap_relnotes.stat,
derby-4857-2a-jirasoap_maven_client.diff, derby-4857-2a-jirasoap_maven_client.stat
>
>
> Somewhat simplified, the release manager (RM) must currently perform the following manual
steps to feed the release note generate the data it needs:
> a) Create manual JIRA filter to select issues addressed by the release.
> b) Save the filter result to disk as XML.
> c) Write/modify the XML parser to be able to parse the report.
> d) Determine and record all JIRA release note attachment ids for the issues requiring
a release note.
> By using the current version of the SOAP API (3.13.5), steps (b) to (d) can be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.