[ https://issues.apache.org/jira/browse/YETUS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820098#comment-15820098 ]
Suraj Acharya edited comment on YETUS-474 at 1/12/17 4:01 AM: -------------------------------------------------------------- I have made the error to be silent. It continues if the files are not present. {code} sacharya@sacharya-MBP:~/repos/yetus$ ./build.sh --release working on version '0.6.0-SNAPSHOT' generating release docs. There is no issue which has the specified version: 0.6.0 mv: target/0.6.0/RELEASENOTES.0.6.0.md: No such file or directory mv: target/0.6.0/CHANGES.0.6.0.md: No such file or directory hard reseting working directory. HEAD is now at 3264cb1 YETUS-474 build.sh --release fails. creating source tarball at '/Users/sacharya/repos/yetus/target/' running maven builds for java components {code} was (Author: sacharya): I have made the error to be silent. It continues if the files are not present. > 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 > Attachments: 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)