On 28/07/2011, at 2:23 AM, Lars Fischer wrote: >> After the git flow release is finnished, both master and develop sit at the >> next -SNAPSHOT version, >> this actually works out nice as it means you can then at some point do a >> "git flow hotfix start..." >> if need be to patch the last release ( which branches from master ). > > This breaks the gitflow master definition: "We consider origin/master > to be the main branch where the source code of HEAD always reflects a > production-ready state." > > But without this restriction, your process should work.
Hrm - I still believe that master would be "production-ready-state" even with the -SNAPSHOT version, the code is in a state that ready for production release. If I did a maven release from there I'd get the same code built, with the only difference being the version number. If I checked out master and did a maven install, I'd expect to get a SNAPSHOT and not something that's going to overwrite existing released artifacts. > It must not match the maven repo, but there should not be a SNAPSHOT-pom on > HEAD As above I beg to differ. > [...] > [INFO] --- maven-release-plugin:2.2:perform (default-cli) @ master --- > [INFO] Checking out the project to perform the release ... > [INFO] Performing a LOCAL checkout from > scm:git:file://D:\dev\projects\maven.master\source\maven.master > [INFO] Executing: cmd.exe /X /C "git clone > file://D\dev\projects\maven.master\source\maven.master > D:\dev\projects\maven.master\source\maven.master\target\checkout" Interesting - I see you have maven.master mentioned twice in the path - what do you have in your SCM settings element? And what is the root path of the git repo, and are you releasing from that directory? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
