[
https://issues.apache.org/jira/browse/DERBY-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586371#action_12586371
]
Rick Hillegas commented on DERBY-3598:
--------------------------------------
Hi Dyre,
I think that this patch will do what you want. However, I would be tempted to
solve this problem a different way. Instead. of specifying the excluded
versions on the command line, I would give releaseSummary.xml a new element for
the excluded version list. That element can have a variable number of version
sub-elements. The purpose of releaseSummary.xml is to hold a number of inputs
which would otherwise make the command line unwieldy.
> 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.0
> Reporter: Dyre Tjeldvoll
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3598.diff
>
>
> 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.
