[
https://issues.apache.org/jira/browse/DERBY-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-3598:
----------------------------------
Attachment: derby-3598.v2.stat
derby-3598.v2.diff
I've attached a new patch (v2) which implements Rick's suggestion. The patch is
rather large because I included some additional changes:
1. Read the current version number from main.properties, so that doesn't have
to be specified in releaseSummary.xml
2. Added excludeVersion as a tag in releaseSummary.xml (there can be any number
of such tags with different values)
3. Refactored identical code from ReleaseNoteGenerator and ChangesGenerator
into a common base class
4. Factored out the duplicated nested class JiraIssue to an ordinary class
5. Removed the nested class GeneratorState
6. Renamed "pamphletFile" to "outputFile" which I found more intuitive
(possibly because English is not my native language)
> Modify ReleaseNoteGenerator and ChangesGenerator to exclude issues that are
> fixed in earlier releases
> -----------------------------------------------------------------------------------------------------
>
> Key: DERBY-3598
> URL: https://issues.apache.org/jira/browse/DERBY-3598
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.4.1.3
> Reporter: Dyre Tjeldvoll
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3598.diff, derby-3598.v2.diff, derby-3598.v2.stat
>
>
> Since we cannot create a Jira filter which selects issues with a set fix
> versions and at the same time EXCLUDE issues with another set of fix
> versions, it would be nice if the *Generator programs could filter out those
> issues already fixed in previously released versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
