Hi group,
I'm working on a legacy application that uses Maven for build, but not for release. For that it has a shell script that, among other things, does a single commit (representing the release) which includes a mix of manual and automated information in the commit message. I'm trying to convert this over to using the Maven Release Plugin. I'm quite familiar with that plugin, so I know that it doesn't typically work like this legacy script does. But in order to give the consumers of this process less change to deal with, I'm wondering if there's any workarounds to include a more-comprehensive commit message for the modified POMs commit (released version) and the tag "commit"? I think I know the answer, but it doesn't hurt to ask (yet) :) I suppose I could cobble together some error-prone multi-line scmCommentPrefix value. This would be ideal, but the question never got answered: http://maven.40175.n5.nabble.com/Is-there-a-way-to-provide-to-Maven-a-custom-SVN-log-message-during-release-prepare-td121487.html Thanks. Best regards, Sander. Sander Verhagen [ [email protected]<mailto:[email protected]> ]
