jgit-flow:release-start issue

[Kyle Bober]

So, I am new to the jgit-flow maven plugin and I am running into an issue starting a release. 

I already have a previously created release branch named: release-1.0.0

When I run : mvn jgitflow:release-start

I am presented with the following failure message :

mvn jgitflow:release-start

[INFO] Scanning for projects...

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Build Order:

[INFO]

[INFO] Parent POM for the Karyon Admin Web Docs

[INFO] karyon-admin-web-docs

[INFO]

[INFO] ------------------------------------------------------------------------

[INFO] Building Parent POM for the Karyon Admin Web Docs 1.0.2-SNAPSHOT

[INFO] ------------------------------------------------------------------------

[INFO]

[INFO] --- jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) @ karyon-admin-web-docs-parent ---

Username: kbober

Password:

[INFO] (develop) Checking for SNAPSHOT version in projects...

[INFO] (develop) Checking dependencies and plugins for snapshots ...

What is the release version for "Parent POM for the Karyon Admin Web Docs"? (net.charter:karyon-admin-web-docs-parent) [1.0.2]:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Parent POM for the Karyon Admin Web Docs ........... FAILURE [ 13.532 s]

[INFO] karyon-admin-web-docs .............................. SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 13.765 s

[INFO] Finished at: 2015-07-16T16:46:38-04:00

[INFO] Final Memory: 15M/256M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal external.atlassian.jgitflow:jgitflow-maven-plugin:1.0-m5.1:release-start (default-cli) on project karyon-admin-web-docs-parent: Error starting release: Error starting release: a release branch [refs/remotes/origin/release-1.0.0] already exists. Finish that first! -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Here is my pom.xml plugin configuration:

<plugin>

<groupId>external.atlassian.jgitflow</groupId>

<artifactId>jgitflow-maven-plugin</artifactId>

<configuration>

<autoVersionSubmodules>true</autoVersionSubmodules>

<noDeploy>true</noDeploy>

<pushFeatures>true</pushFeatures>

<pushReleases>true</pushReleases>

<pushHotfixes>true</pushHotfixes>

<flowInitContext>

<masterBranchName>master</masterBranchName>

         <developBranchName>develop</developBranchName>

        <featureBranchPrefix>feature-</featureBranchPrefix>

        <releaseBranchPrefix>release-</releaseBranchPrefix>

        <hotfixBranchPrefix>hotfix-</hotfixBranchPrefix>

        <versionTagPrefix>karyon-admin-web-docs-tag-</versionTagPrefix>

</flowInitContext>

</configuration>

</plugin>

I do not want to have to delete the remote release branch and am curious as to how I finish the release-1.0.0 so the plugin will work???

Thanks,

Kyle 

[Jeffrey Bell]

The plugin enforces only a single release branch at a time. The release-finish goal takes care of merging that branch into master, creating a tag, and merging master into develop. If there are multiple release branches, the merging that takes place in the release-finish will likely have merge conflicts that cannot be handled by the plugin.

[Virat]

Anyway we can solve this ? 

[Cedric Teyton]

I have the same issue. 

It seems the plugin allows to keep and publish the "release" branches, but then i can't publish others releases without deleting the remote branch... 

However in the gitflow model, a "release" branch can contain multiple release tags. 

[Krishna Gorthi]

Upon running release-start, should the -SNAPSHOT suffix in version under release branch be removed ? If not at what point -SNAPSHOT in version under release branch is turned into a non-snapshot version ?
Currently, I am running into an issue when I do release-start, I see the development SNAPHOT version is copied under release branch and when run release-finish, it complains that
"

Error verifying version state in poms: Some reactor projects contain SNAPSHOT versions!
"
The only way, I have been able to make this step to finish is by my manually updating the SNAPSHOT versions to release versions and running the release-start goal
What am I missing here ? Is this expected ?