Improvements for usage in CI environment about gradle-release HOT 1 CLOSED

Hi Moritz, Thank you for your interest in this project. Looking forward to a pull request. :)

1. There was an issue with using project.getProjectDir(), if I remember correctly I believe this fails when using sub-modules. The plugin assumes that there is one SCM per project - and that sub-modules belong to the same SCM tree. This means that the SCM commands must be executed at the root of the project. If I remember correctly, project.getProjectDir() will give me the project directory of the current project (or sub-module when Gradle is in one), which caused the plugin to fail because the SCM commands would get executed within the sub-module's directory instead of the project's root. Do you have a project that uses sub-modules that you could test your change with?
2. This one is a little tricky. I don't think it's a good idea for the username/password to be hard-coded in the build.gradle file ( at least, my ops guys wouldn't like this ). A better approach may be to have one of your sys-admins set up the access differently for your Jenkins user - or have them SSH in to the box and log-in through svn and have the password saved that way. If that's not an option, I think it'd be better if you had them passed in via -P or -D parameters.

from gradle-release.