I've checked your output and these lines are parsed as expected.
Somehow the output was different during the release, because that didn't
recognize any changed files.
Mark Struberg told me that the GIT output is written to a file somewhere
under target.
Otherwise I could use some debug-logging, which contains the git-output as
well.
Robert
Op Fri, 04 Jan 2013 22:12:39 +0100 schreef Julien Silland
<[email protected]>:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
