Hello Mark, 2011/7/25 Mark Derricutt <[email protected]> > > We're using gitflow/maven quite nicely, I use for my release plugin: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.1</version> > <configuration> > <goals>deploy</goals> > <pushChanges>false</pushChanges> > <localCheckout>true</localCheckout> > </configuration> > </plugin>
> In this configuration maven does a local checkout, and doesn't require a git > push during release. > This means after a maven release, I do my git-flow release, THEN push the > master/develop branch to my origin. I'm sorry, I don't understand. You first run the maven-release-plugin? On which gitflow-branch (develop, feature, release)? I think the maven release results in a NON-SNAPSHOT tag and finaly creates a new SNAPSHOT-pom on head. If you now do finish the gitflow release, this SNAPSHOT-pom will go on the master branch. But gitflow defines master as the stable production branch. There should no SNAPSHOT-pom exist on the master branch. Am I mistaken? Regards, Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
