[
https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4857:
----------------------------
Attachment: RELEASE-NOTES.html
I volunteer to test-drive the 3a and 4a patch on Windows. After doing 'mvn
clean install' on maven2 and tools/release/jirasoap, I sync up the latest
codeline from trunk and apply 3a and 4a patch. I was not able to build the
RELESE-NOTES.html using 'ant genrelnotes'. However, the createreleasenote.sh
script works for me. I am not sure why I am getting an error from
FilteredIssueListen. I got an error as jirasoap.FilteredIssueLister is fetching
issue. Error print out as:"Exception in thread "main"
java.lang.IllegalArgumentException: version 'true' doesn't exist
at org.apache.derbyBuild.jirasoap.FilteredIssueLister.getVersion(Filtere
dIssueLister.java:487)
at org.apache.derbyBuild.jirasoap.FilteredIssueLister.prepareReleaseNote
s(FilteredIssueLister.java:245)
at org.apache.derbyBuild.jirasoap.FilteredIssueLister.main(FilteredIssue
Lister.java:610)"
I was still able to generate a RELEASE-NOTES.html. I attach the file for
reference. I did not change releaseSummary.html to reflect my build
environment when I run the script.
> 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-4a-jirasoap_ant_integration.diff,
> derby-4857-4a-jirasoap_ant_integration.stat, 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.
