svn credentials specified in project configuration are never used.

[Paul Carduner]

What's more, the package builder script fails to prompt the user for *their* svn credentials. When svn is run as a subprocess, the username and password prompts are not passed from svn to the parent process and the build script appears to hang, when in fact it is just waiting for user input even though the user cannot see a prompt.

Possible solutions: fix the way keas.build does subprocesses so all prompts get forwarded until the subprocess is complete (not sure how to do this) or make all calls to svn specify --username and --password based on settings in the project configuration file. This however could be a security risk for some people and also forgoes the opportunity to track which user actually made a release.

[Adam Groszer (agroszer)]

I think I'll add an option for this, because we need to build with buildBOT and that server won't ever have svn credentials.