[
https://issues.apache.org/jira/browse/JCRVLT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010142#comment-18010142
]
Joerg Hoh commented on JCRVLT-799:
----------------------------------
I think that I followed the documentation at
https://jackrabbit.apache.org/filevault/howto_release.html, but I ended up
creating a release 4.0.0-SNAPSHOT (!!), and which then failed in {{mvn
release:perform}}.
It's a thing that there is a check for an updated RELEASE-NOTES.txt file, but
we should move this check at the beginning of the {{mvn release:prepare}}
execution, so if missed, it can be fixed without rolling back the release,
fixing it and then starting again.
> mvn deploy fails on RELEASE-NOTES.txt check
> -------------------------------------------
>
> Key: JCRVLT-799
> URL: https://issues.apache.org/jira/browse/JCRVLT-799
> Project: Jackrabbit FileVault
> Issue Type: Task
> Reporter: Julian Reschke
> Priority: Minor
>
> ..because the check operates using the project version from the pom, not
> `$version`.
> Workaround: do `mvn release:prepare` first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
