Hi Benson,
there's actually still one thing bothering me (and which also blocked me
for doing this release):
How can it be that there's a PR (#17) on SCM when the issue is already
fixed?
From other issues I remember that for some users upgrading to SCM-1.9.1
did help, though for others it didn't.
It's like they have a comparable issue, but the project structure/usecase
is different.
According to the release notes of SCM-1.9.2 there's no change on the
git-exe part, so you should be able to confirm that
maven-release-plugin-2.5 + scm-1.9.1 will do the trick (for your issue).
thanks,
Robert
Op Sat, 13 Sep 2014 18:51:03 +0200 schreef Benson Margulies
<[email protected]>:
All this will do is pick up SCM fixes. Still, that seems too big for
2.5.1
-- but definitely too small for 3.0. So I'm setting up for 2.6.0. If
someone disagrees I will change it again.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
