I understand the root issue is not from the release plugin itself but from the SCM implementation. Though, I have to mention that the plugin was error'ing out when I had left modified files before running maven:prepare.
My git version is: 1.7.7.5 (Apple Git-26) Here's a sample output of git status --porcelain: M pom.xml A foo-archetype/pom.xml ?? phonebook/ This is respectively for a modified file, a new file and an untracked folder. I have no idea what's that character in between the beginning of the line and the 'M' for the modified file. -- Julien Silland On Friday, January 4, 2013 at 12:55 PM, Robert Scholte wrote: > The real issue is https://jira.codehaus.org/browse/SCM-709 > To solve it we could really use some feedback on this issue: > - which version of GIT are you using? > - what is the output of 'git status --porcelain' if a file is modified? > > Robert > > Op Fri, 04 Jan 2013 21:00:40 +0100 schreef Julien Silland > <[email protected] (mailto:[email protected])>: > > > Thanks for the pointer to the bug. I've configured my project to use the > > 2.3.2 version of the release plugin and things are working as expected. > > I haven't explored switching to different scm version dependency. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > (mailto:[email protected]) > For additional commands, e-mail: [email protected] > (mailto:[email protected]) > >
