[
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-1a-jirasoap_relnotes.stat
derby-4857-1a-jirasoap_relnotes.diff
Attaching patch 1a, which contains the first revision of the described tool.
Maven2 is required, to build do 'mvn -Pbuildclient'. There exists another
target in case the WSDL file has to be updated: 'mvn -Pfetch-wsdl'.
'mvn clean' cleans up generated files.
To test, run:
o java -jar target/JiraSOAP-LATEST-jar-with-dependencies.jar
o read the help text, re-run with proper arguments :)
o run 'ant relnotes' pointing at the file generated above to generate the
release notes (as HTML)
-- Apache Derby SOAP client for generating release notes --
The main purpose of this client is to fetch the required information from
JIRA, such that the release manager can generate the release notes.
This tool does not generate the release notes, but provides some of the
information for the tool doing that.
Usage:
o <USER> <PASSWORD> <VERSION> <FILTERID> <DESTINATION_FILE> [<REMOVE_ISSUES>]
generates a list of fixed issues for the specified release version,
which can be processed by the ReleaseNotesGenerator tool
o <USER> <PASSWORD> ancestors <VERSION>
prints the ancestors of the specified version
(only released versions can be ancestor)
Argument values:
o VERSION
Derby version string, i.e. 10.6.2.1
o FILTERID
JIRA id, only digits allowed
---
What remains:
o more testing
o does the client to anything useful?
o does it need to do anything else?
o integrate with 'ant relnotes' target?
> 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
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-4857-1a-jirasoap_relnotes.diff,
> derby-4857-1a-jirasoap_relnotes.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.
