[
https://issues.apache.org/jira/browse/SCM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963345#comment-17963345
]
ASF GitHub Bot commented on SCM-841:
------------------------------------
jira-importer commented on issue #1067:
URL: https://github.com/apache/maven-scm/issues/1067#issuecomment-2964643738
**[Konrad
Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)**
commented
No I didn't try it out. But I would propose to change the way how SVN is
called then. When the SVN command is currently not being triggered with an
input stream being properly allocated I would favor to then change that to
allow for a true interactive modes here. Otherwise you can only pass the
credentials via the regular CLI parameters with the known drawbacks (see
https://maven.apache.org/guides/mini/guide-encryption.html#Tips, Prompting for
Passwords).
> Support --force-interactive option introduced with SVN 1.8
> ----------------------------------------------------------
>
> Key: SCM-841
> URL: https://issues.apache.org/jira/browse/SCM-841
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Affects Versions: 1.9.5
> Reporter: Konrad Windszus
> Priority: Major
>
> With SVN 1.8 the additional option {{--force-interactive}} has been
> introduced with this commit:
> http://svn.apache.org/viewvc?view=revision&revision=1424037.
> This option is not documented at
> http://svnbook.red-bean.com/en/1.8/svn.ref.svn.html. But the CLI exposes the
> following (via {{svn st --help}}
> {code}
> --non-interactive : do no interactive prompting (default is to prompt
> only if standard input is a terminal device)
> --force-interactive : do interactive prompting even if standard input
> is not a terminal device
> {code}
> It seems that it always runs by default in non-interactive mode even with
> {{useNonInteractive}} set to false
> (https://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svn-commons/svn-settings.html)
> when being triggered from the maven release plugin, therefore with {{mvn
> release:prepare}} you might see the following issue
> {code}
> [INFO] --- maven-release-plugin:2.5.1:prepare (default-cli) @ xxx ---
> [INFO] Resuming release from phase 'scm-commit-release'
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd <some directory> && svn commit --file
> /var/folders/rm/vlg2h6m16mb0f65djmnb12xr0000gq/T/maven-scm-1099976641.commit
> --targets
> /var/folders/rm/vlg2h6m16mb0f65djmnb12xr0000gq/T/maven-scm-3840927493290123998-targets
> [INFO] Working directory: <some directory>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3.664 s
> [INFO] Finished at: 2017-02-05T10:58:28+00:00
> [INFO] Final Memory: 14M/247M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on
> project xxx: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: E215004: Authentication failed and interactive prompting is
> disabled; see the --force-interactive option
> [ERROR] svn: E215004: Commit failed (details follow):
> [ERROR] svn: E215004: No more credentials or we tried too many times.
> [ERROR] Authentication failed
> {code}
> Even though SVN was triggered without the option {{\-\-non-interactive}} it
> still won't run in interactive mode due to the change in 1.8. Therefore the
> {{svn-setttings.xml}} should support to enable the new option
> {{\-\-force-interactive}} so that the SVN will interactively ask for the
> credentials (instead of being forced to pass that via {{-Dusername and
> -Dpassword}} when triggering the mvn goal).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
