You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Suraj Acharya (JIRA)" <ji...@apache.org> on 2017/01/10 16:56:58 UTC
[jira] [Commented] (YETUS-474) master build broken
[ https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815490#comment-15815490 ]
Suraj Acharya commented on YETUS-474:
-------------------------------------
Seems like it was fixed by {{3acbea7cd850e54af91e3055558cc41fa5c99b8d}}
{code}
sacharya@sacharya-MBP:~/repos/yetus$ ./build.sh --release
working on version '0.5.0-SNAPSHOT'
generating release docs.
=======================================
0.5.0: Error:0, Warning:0
hard reseting working directory.
{code}
> 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
> Priority: Blocker
>
> {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)