[jira] [Commented] (YETUS-474) Option to releasedocmaker to write empty files when no JIRA issues match

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774804#comment-16774804 ] 

Allen Wittenauer commented on YETUS-474:
----------------------------------------

-03:
* add --empty to releasedocmaker and to the maven plugin that will not abort when a version is empty
* changed the release notes generation for Yetus to pass in this flag

> Option to releasedocmaker to write empty files when no JIRA issues match
> ------------------------------------------------------------------------
>
>                 Key: YETUS-474
>                 URL: https://issues.apache.org/jira/browse/YETUS-474
>             Project: Yetus
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.5.0
>            Reporter: Sean Busbey
>            Assignee: Allen Wittenauer
>            Priority: Blocker
>         Attachments: Bump_patch_to_0.99.98.patch, Bump_patch_to_0.99.99.patch, YETUS-474-01.patch, YETUS-474-02.patch, YETUS-474.03.patch, YETUS-474.patch
>
>
> {code}
>  ./build.sh --release
> working on version '0.5.0-SNAPSHOT'
> generating release docs.
> There is no issue which has the specified version: 0.5.0
> mv: rename target/0.5.0/RELEASENOTES.0.5.0.md to target/RELEASENOTES.md: No such file or directory
> {code}
> I'm guessing it's the version bump and an edge case in handling RDM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)