[
https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830083#comment-15830083
]
Suraj Acharya commented on YETUS-474:
-------------------------------------
I see your point my point of view was that it should throw all the errors at
one time and continue. Fixing one problem at a time can be tiring and time
consuming.
Also, somethings might be out of your hand, example JIRA version. In such a
scenario you might want to see all the errors and try to tackle them together.
> master build broken
> -------------------
>
> 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: Suraj Acharya
> Priority: Blocker
> Fix For: 0.5.0
>
> 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.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
(v6.3.4#6332)
