[
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-5a-minor_tweaks.diff
Thanks for testing the client further, Rick.
Regarding your comments:
a) I added the directory to the svn:ignore property of tools/release/jirasoap.
Note that the directory is deleted when/if you run 'ant clean' from
tools/release.
b) You will only see those numbers when you are downloading stuff you need,
but that you don't have locally. In any case, adding '--batch-mode' to the exec
task made them go away (maven will still notify you of downloads, but not use
the download meter).
I also modified the printout regarding the summary file and the exclude list
(which isn't used any more).
Attaching patch 5a, which addresses the issues above. Committed to trunk with
revision 1030383.
> 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,
> derby-4857-3a-jirasoap_relnotesgen_changes.diff,
> derby-4857-3a-jirasoap_relnotesgen_changes.stat,
> derby-4857-3b-jirasoap_relnotesgen_changes.diff,
> derby-4857-4a-jirasoap_ant_integration.diff,
> derby-4857-4a-jirasoap_ant_integration.stat,
> derby-4857-4b-jirasoap_ant_integration.diff, derby-4857-5a-minor_tweaks.diff,
> RELEASE-NOTES.html
>
>
> 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.
