You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Chris <sh...@yahoo.com> on 2009/03/26 22:56:17 UTC
SCM requires that command line svn be used?
I'm trying to configure my pom to use an <scm>. We use Subversion. When
I run it, I get the error "'svn' is not recognized as an internal or
external command, operable program or batch file.". I take it this means
that svn.exe needs to be on the path, and the plugin is shelling out to
access it.
This is obviously flaky and error prone. In Ant, I can use SvnAnt to
access svn directly, using java alone.
Is it possible to configure Maven to use one of the svn-java libraries
instead of the command line client?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: SCM requires that command line svn be used?
Posted by "Nord, James" <JN...@nds.com>.
Needed to also add should this be a dependency of the javadvn
implementation instead?
<dependency>
<groupId>com.sun.jna</groupId>
<artifactId>jna</artifactId>
<version>3.0.5</version>
</dependency>
/James
> -----Original Message-----
> From: Nord, James [mailto:JNord@nds.com]
> Sent: 06 April 2009 17:28
> To: Maven Users List
> Subject: RE: SCM requires that command line svn be used?
>
> Hi Oliver,
>
> Is there any documentation on how to configure this.
>
> Looking at the source I have tried adding the library as
> dependencies to the scm plug-in and running
>
> mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status
>
> However this fails to use stored local credentials and fails
> with [INFO] [scm:status] [INFO] SVN status directory:
> D:\workspaces\simpleProject\ [ERROR] Provider message:
> [ERROR] SVN status failed.
> [ERROR] Command output:
> [ERROR] svn: Authentication required for
> '<https://svnrepo.myco.com:443> Welcome to My CO.s Subversion
> Repository'
>
> If I just run mvn scm:status it works fine - but uses svn.exe instead.
>
> Authentication is configured in usual svn location for
> windows %APPDATA%\Subversion and is in wincrypt form.
>
> I have authentication present for multiple servers -however I
> tried removing all but the one in question and it still fails.
>
> /James
>
> > -----Original Message-----
> > From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com]
> On Behalf
> > Of Olivier Lamy
> > Sent: 26 March 2009 22:15
> > To: Maven Users List
> > Subject: Re: SCM requires that command line svn be used?
> >
> > Hi,
> > It's possible with the javasvn implementation. This has been moved
> > recently from the asf repository due to license issue.
> > Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
> > It will be released after the maven-scm release.
> >
> > HTH,
> > --
> > Olivier
> >
> > 2009/3/26 Chris <sh...@yahoo.com>:
> > > I'm trying to configure my pom to use an <scm>. We use
> Subversion.
> > > When I run it, I get the error "'svn' is not recognized as
> > an internal
> > > or external command, operable program or batch file.". I
> > take it this
> > > means that svn.exe needs to be on the path, and the plugin
> > is shelling out to access it.
> > >
> > > This is obviously flaky and error prone. In Ant, I can use
> > SvnAnt to
> > > access svn directly, using java alone.
> > >
> > > Is it possible to configure Maven to use one of the
> > svn-java libraries
> > > instead of the command line client?
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> **************************************************************
> ************************
> This e-mail is confidential, the property of NDS Ltd and
> intended for the addressee only. Any dissemination, copying
> or distribution of this message or any attachments by anyone
> other than the intended recipient is strictly prohibited. If
> you have received this message in error, please immediately
> notify the postmaster@nds.com and destroy the original
> message. Messages sent to and from NDS may be monitored. NDS
> cannot guarantee any message delivery method is secure or
> error-free. Information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or contain
> viruses. We do not accept responsibility for any errors or
> omissions in this message and/or attachment that arise as a
> result of transmission. You should carry out your own virus
> checks before opening any attachment. Any views or opinions
> presented are solely those of the author and do not
> necessarily represent those of NDS.
>
> To protect the environment please do not print this e-mail
> unless necessary.
>
> NDS Limited Registered Office: One London Road, Staines,
> Middlesex, TW18 4EX, United Kingdom. A company registered in
> England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
> **************************************************************
> ************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Javasvn patch
Posted by "Nord, James" <JN...@nds.com>.
Hi Oliver,
I have found and fixed a couple of bugs.
1) support wincrypt encrypted passwords on windows
2) support running info correctly. (it would strip any file and run only
on the base directory) thus an request for info on /path/to/file would
give you the results for /path/to/ it would also only honour the first
entry in the file set.
Tested on windows - Linux/Mac/Solaris/BSD millage may vary.
/James
> -----Original Message-----
> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] On
> Behalf Of Olivier Lamy
> Sent: 06 April 2009 18:46
> To: Maven Users List
> Subject: Re: SCM requires that command line svn be used?
>
> Hi,
> I have tested only with username/password in the cli :
> -Dusername= -Dpassword=
>
> 2009/4/6 Nord, James <JN...@nds.com>:
> > Hi Oliver,
> >
> > Is there any documentation on how to configure this.
> >
> > Looking at the source I have tried adding the library as
> dependencies
> > to the scm plug-in and running
> >
> > mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status
> >
> > However this fails to use stored local credentials and fails with
> > [INFO] [scm:status] [INFO] SVN status directory:
> > D:\workspaces\simpleProject\ [ERROR] Provider message:
> > [ERROR] SVN status failed.
> > [ERROR] Command output:
> > [ERROR] svn: Authentication required for
> > '<https://svnrepo.myco.com:443> Welcome to My CO.s
> Subversion Repository'
> >
> > If I just run mvn scm:status it works fine - but uses
> svn.exe instead.
> >
> > Authentication is configured in usual svn location for windows
> > %APPDATA%\Subversion and is in wincrypt form.
> >
> > I have authentication present for multiple servers -however I tried
> > removing all but the one in question and it still fails.
> >
> > /James
> >
> >> -----Original Message-----
> >> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com]
> On Behalf
> >> Of Olivier Lamy
> >> Sent: 26 March 2009 22:15
> >> To: Maven Users List
> >> Subject: Re: SCM requires that command line svn be used?
> >>
> >> Hi,
> >> It's possible with the javasvn implementation. This has been moved
> >> recently from the asf repository due to license issue.
> >> Now it's here :
> http://code.google.com/p/maven-scm-provider-svnjava/
> >> It will be released after the maven-scm release.
> >>
> >> HTH,
> >> --
> >> Olivier
> >>
> >> 2009/3/26 Chris <sh...@yahoo.com>:
> >> > I'm trying to configure my pom to use an <scm>. We use
> Subversion.
> >> > When I run it, I get the error "'svn' is not recognized as
> >> an internal
> >> > or external command, operable program or batch file.". I
> >> take it this
> >> > means that svn.exe needs to be on the path, and the plugin
> >> is shelling out to access it.
> >> >
> >> > This is obviously flaky and error prone. In Ant, I can use
> >> SvnAnt to
> >> > access svn directly, using java alone.
> >> >
> >> > Is it possible to configure Maven to use one of the
> >> svn-java libraries
> >> > instead of the command line client?
> >> >
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
Re: SCM requires that command line svn be used?
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
I have tested only with username/password in the cli : -Dusername= -Dpassword=
2009/4/6 Nord, James <JN...@nds.com>:
> Hi Oliver,
>
> Is there any documentation on how to configure this.
>
> Looking at the source I have tried adding the library as dependencies to
> the scm plug-in and running
>
> mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status
>
> However this fails to use stored local credentials and fails with
> [INFO] [scm:status]
> [INFO] SVN status directory: D:\workspaces\simpleProject\
> [ERROR] Provider message:
> [ERROR] SVN status failed.
> [ERROR] Command output:
> [ERROR] svn: Authentication required for '<https://svnrepo.myco.com:443>
> Welcome to My CO.s Subversion Repository'
>
> If I just run mvn scm:status it works fine - but uses svn.exe instead.
>
> Authentication is configured in usual svn location for windows
> %APPDATA%\Subversion and is in wincrypt form.
>
> I have authentication present for multiple servers -however I tried
> removing all but the one in question and it still fails.
>
> /James
>
>> -----Original Message-----
>> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] On
>> Behalf Of Olivier Lamy
>> Sent: 26 March 2009 22:15
>> To: Maven Users List
>> Subject: Re: SCM requires that command line svn be used?
>>
>> Hi,
>> It's possible with the javasvn implementation. This has been
>> moved recently from the asf repository due to license issue.
>> Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
>> It will be released after the maven-scm release.
>>
>> HTH,
>> --
>> Olivier
>>
>> 2009/3/26 Chris <sh...@yahoo.com>:
>> > I'm trying to configure my pom to use an <scm>. We use Subversion.
>> > When I run it, I get the error "'svn' is not recognized as
>> an internal
>> > or external command, operable program or batch file.". I
>> take it this
>> > means that svn.exe needs to be on the path, and the plugin
>> is shelling out to access it.
>> >
>> > This is obviously flaky and error prone. In Ant, I can use
>> SvnAnt to
>> > access svn directly, using java alone.
>> >
>> > Is it possible to configure Maven to use one of the
>> svn-java libraries
>> > instead of the command line client?
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> **************************************************************************************
> This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
>
> To protect the environment please do not print this e-mail unless necessary.
>
> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
> **************************************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM requires that command line svn be used?
Posted by doddalas <vi...@gmail.com>.
Hi,
Yes I have provided credentials in Maven settings.xml and also while
running the job, as parameters like -Dusername, -Dpassword. Even then I am
getting above error.
Vijay
On Thu, Feb 13, 2014 at 11:45 PM, Baptiste MATHUS-2 [via Maven] <
ml-node+s40175n5784666h1@n5.nabble.com> wrote:
> It says authentication required. Did you provide/configure the necessary
> credentials?
> Le 13 févr. 2014 12:21, "doddalas" <[hidden email]<http://user/SendEmail.jtp?type=node&node=5784666&i=0>>
> a écrit :
>
> > Hi,
> >
> > I am getting the same error. Can you please help me if you have fixed
> this
> > issue. Do we need to configure anything specifically for https svn URLs?
> I
> > have given credentials in maven settings and svn configuration in pom
> > files.
> > Any my release plugin is as follows:
> >
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-release-plugin</artifactId>
> > <version>2.4.2</version>
> > <dependencies>
> > <dependency>
> >
> > <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
> >
> > <artifactId>maven-scm-provider-svnjava</artifactId>
> > <version>1.6</version>
> > </dependency>
> > </dependencies>
> > <configuration>
> > <providerImplementations>
> > <svn>javasvn</svn>
> > </providerImplementations>
> > <tagBase>
> > https://mydomain.com/svn/New_FW/CI_POC/tags</tagBase>
> >
> > <mavenExecutorId>forked-path</mavenExecutorId>
> > </configuration>
> > </plugin>
> > PFB the error that I am getting:
> >
> > [INFO] Building Service 1.0.0-SNAPSHOT
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO]
> > [INFO] --- maven-release-plugin:2.4.2:prepare (default-cli) @ Service
> ---
> > [INFO] Change the default 'svn' provider implementation to 'javasvn'.
> > [INFO] Verifying that there are no local modifications...
> > [INFO] ignoring changes on: **\release.properties, **\pom.xml.next,
> > **\pom.xml.releaseBackup, **\pom.xml.backup, **\pom.xml.branch,
> > **\pom.xml.tag
> > [INFO] SVN status directory:
> > D:\Softwares\jenkins\jobs\Perform_Release\workspace
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Service ........................................... FAILURE
> > [14.743s]
> > [INFO] ServiceEJB ........................................ SKIPPED
> > [INFO] SpringMVC323REST .................................. SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 17.859s
> > [INFO] Finished at: Thu Feb 13 10:37:59 IST 2014
> > [INFO] Final Memory: 9M/55M
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
> (default-cli)
> > on
> > project Service: Unable to check for local modifications
> > [ERROR] Provider message:
> > [ERROR] SVN status failed.
> > [ERROR] Command output:
> > [ERROR] svn: Authentication required for '<https://mydomain.com:443>'
> > [ERROR] -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
> > (default-cli) on project Service: Unable to check for local
> modifications
> > Provider message:
> > SVN status failed.
> > Command output:
> > svn: Authentication required for '<https://mydomain.com:443>'
> > at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> >
> >
> >
> > --
> > View this message in context:
> >
> http://maven.40175.n5.nabble.com/SCM-requires-that-command-line-svn-be-used-tp119251p5784375.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=5784666&i=1>
> > For additional commands, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=5784666&i=2>
> >
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/SCM-requires-that-command-line-svn-be-used-tp119251p5784666.html
> To unsubscribe from SCM requires that command line svn be used?, click
> here<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=119251&code=dmlqYXlkMTUwOEBnbWFpbC5jb218MTE5MjUxfDE2ODEzNzQzMTQ=>
> .
> NAML<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://maven.40175.n5.nabble.com/SCM-requires-that-command-line-svn-be-used-tp119251p5784713.html
Sent from the Maven - Users mailing list archive at Nabble.com.
RE: SCM requires that command line svn be used?
Posted by Baptiste Mathus <bm...@batmat.net>.
It says authentication required. Did you provide/configure the necessary
credentials?
Le 13 févr. 2014 12:21, "doddalas" <vi...@gmail.com> a écrit :
> Hi,
>
> I am getting the same error. Can you please help me if you have fixed this
> issue. Do we need to configure anything specifically for https svn URLs? I
> have given credentials in maven settings and svn configuration in pom
> files.
> Any my release plugin is as follows:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.4.2</version>
> <dependencies>
> <dependency>
>
> <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>
> <artifactId>maven-scm-provider-svnjava</artifactId>
> <version>1.6</version>
> </dependency>
> </dependencies>
> <configuration>
> <providerImplementations>
> <svn>javasvn</svn>
> </providerImplementations>
> <tagBase>
> https://mydomain.com/svn/New_FW/CI_POC/tags</tagBase>
>
> <mavenExecutorId>forked-path</mavenExecutorId>
> </configuration>
> </plugin>
> PFB the error that I am getting:
>
> [INFO] Building Service 1.0.0-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-release-plugin:2.4.2:prepare (default-cli) @ Service ---
> [INFO] Change the default 'svn' provider implementation to 'javasvn'.
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **\release.properties, **\pom.xml.next,
> **\pom.xml.releaseBackup, **\pom.xml.backup, **\pom.xml.branch,
> **\pom.xml.tag
> [INFO] SVN status directory:
> D:\Softwares\jenkins\jobs\Perform_Release\workspace
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Service ........................................... FAILURE
> [14.743s]
> [INFO] ServiceEJB ........................................ SKIPPED
> [INFO] SpringMVC323REST .................................. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 17.859s
> [INFO] Finished at: Thu Feb 13 10:37:59 IST 2014
> [INFO] Final Memory: 9M/55M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli)
> on
> project Service: Unable to check for local modifications
> [ERROR] Provider message:
> [ERROR] SVN status failed.
> [ERROR] Command output:
> [ERROR] svn: Authentication required for '<https://mydomain.com:443>'
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
> (default-cli) on project Service: Unable to check for local modifications
> Provider message:
> SVN status failed.
> Command output:
> svn: Authentication required for '<https://mydomain.com:443>'
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/SCM-requires-that-command-line-svn-be-used-tp119251p5784375.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: SCM requires that command line svn be used?
Posted by doddalas <vi...@gmail.com>.
Hi,
I am getting the same error. Can you please help me if you have fixed this
issue. Do we need to configure anything specifically for https svn URLs? I
have given credentials in maven settings and svn configuration in pom files.
Any my release plugin is as follows:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.2</version>
<dependencies>
<dependency>
<groupId>com.google.code.maven-scm-provider-svnjava</groupId>
<artifactId>maven-scm-provider-svnjava</artifactId>
<version>1.6</version>
</dependency>
</dependencies>
<configuration>
<providerImplementations>
<svn>javasvn</svn>
</providerImplementations>
<tagBase>https://mydomain.com/svn/New_FW/CI_POC/tags</tagBase>
<mavenExecutorId>forked-path</mavenExecutorId>
</configuration>
</plugin>
PFB the error that I am getting:
[INFO] Building Service 1.0.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.4.2:prepare (default-cli) @ Service ---
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **\release.properties, **\pom.xml.next,
**\pom.xml.releaseBackup, **\pom.xml.backup, **\pom.xml.branch,
**\pom.xml.tag
[INFO] SVN status directory:
D:\Softwares\jenkins\jobs\Perform_Release\workspace
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Service ........................................... FAILURE [14.743s]
[INFO] ServiceEJB ........................................ SKIPPED
[INFO] SpringMVC323REST .................................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 17.859s
[INFO] Finished at: Thu Feb 13 10:37:59 IST 2014
[INFO] Final Memory: 9M/55M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on
project Service: Unable to check for local modifications
[ERROR] Provider message:
[ERROR] SVN status failed.
[ERROR] Command output:
[ERROR] svn: Authentication required for '<https://mydomain.com:443>'
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
(default-cli) on project Service: Unable to check for local modifications
Provider message:
SVN status failed.
Command output:
svn: Authentication required for '<https://mydomain.com:443>'
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
--
View this message in context: http://maven.40175.n5.nabble.com/SCM-requires-that-command-line-svn-be-used-tp119251p5784375.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: SCM requires that command line svn be used?
Posted by "Nord, James" <JN...@nds.com>.
Hi Oliver,
Is there any documentation on how to configure this.
Looking at the source I have tried adding the library as dependencies to
the scm plug-in and running
mvn -Dmaven.scm.provider.svn.implementation=javasvn scm:status
However this fails to use stored local credentials and fails with
[INFO] [scm:status]
[INFO] SVN status directory: D:\workspaces\simpleProject\
[ERROR] Provider message:
[ERROR] SVN status failed.
[ERROR] Command output:
[ERROR] svn: Authentication required for '<https://svnrepo.myco.com:443>
Welcome to My CO.s Subversion Repository'
If I just run mvn scm:status it works fine - but uses svn.exe instead.
Authentication is configured in usual svn location for windows
%APPDATA%\Subversion and is in wincrypt form.
I have authentication present for multiple servers -however I tried
removing all but the one in question and it still fails.
/James
> -----Original Message-----
> From: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] On
> Behalf Of Olivier Lamy
> Sent: 26 March 2009 22:15
> To: Maven Users List
> Subject: Re: SCM requires that command line svn be used?
>
> Hi,
> It's possible with the javasvn implementation. This has been
> moved recently from the asf repository due to license issue.
> Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
> It will be released after the maven-scm release.
>
> HTH,
> --
> Olivier
>
> 2009/3/26 Chris <sh...@yahoo.com>:
> > I'm trying to configure my pom to use an <scm>. We use Subversion.
> > When I run it, I get the error "'svn' is not recognized as
> an internal
> > or external command, operable program or batch file.". I
> take it this
> > means that svn.exe needs to be on the path, and the plugin
> is shelling out to access it.
> >
> > This is obviously flaky and error prone. In Ant, I can use
> SvnAnt to
> > access svn directly, using java alone.
> >
> > Is it possible to configure Maven to use one of the
> svn-java libraries
> > instead of the command line client?
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: SCM requires that command line svn be used?
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
It's possible with the javasvn implementation. This has been moved
recently from the asf repository due to license issue.
Now it's here : http://code.google.com/p/maven-scm-provider-svnjava/
It will be released after the maven-scm release.
HTH,
--
Olivier
2009/3/26 Chris <sh...@yahoo.com>:
> I'm trying to configure my pom to use an <scm>. We use Subversion. When I
> run it, I get the error "'svn' is not recognized as an internal or external
> command, operable program or batch file.". I take it this means that svn.exe
> needs to be on the path, and the plugin is shelling out to access it.
>
> This is obviously flaky and error prone. In Ant, I can use SvnAnt to access
> svn directly, using java alone.
>
> Is it possible to configure Maven to use one of the svn-java libraries
> instead of the command line client?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org