[
https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923603#action_12923603
]
Rick Hillegas commented on DERBY-4857:
--------------------------------------
Thanks for the advice about how to test-drive the patch, Kristian. I reverted
ReportParser.java, then did "ant clobber" followed by "ant all". Now I see this
build error:
[echo] building generated sanity info
[java] Warning: Lookahead adequacy checking not being performed since
option LOOKAHEAD is more than 1. Set option FORCE_LA_CHECK to true to force
checking.
[javac]
/Users/rh161140/derby/mainline/trunk/java/build/org/apache/derbyBuild/ChangesFileGenerator.java:200:
cannot find symbol
[javac] symbol : variable bugListDoc
[javac] location: class org.apache.derbyBuild.ChangesFileGenerator
[javac] for (Iterator i = JiraIssue.createJiraIssueList(
bugListDoc, excludeReleaseIDList, reportParser ).iterator(); i.hasNext(); )
[javac] ^
[javac] 1 error
BUILD FAILED
/Users/rh161140/derby/mainline/trunk/build.xml:526: The following error
occurred while executing this line:
/Users/rh161140/derby/mainline/trunk/build.xml:561: The following error
occurred while executing this line:
/Users/rh161140/derby/mainline/trunk/java/build/build.xml:59: The following
error occurred while executing this line:
/Users/rh161140/derby/mainline/trunk/java/build/org/apache/derbyBuild/build.xml:53:
Compile failed; see the compiler error output for details.
> 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.0.0
> 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.
