[ 
https://issues.apache.org/jira/browse/SCM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962371#comment-17962371
 ] 

ASF GitHub Bot commented on SCM-641:
------------------------------------

jira-importer commented on issue #849:
URL: https://github.com/apache/maven-scm/issues/849#issuecomment-2964629245

   **[Robert 
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
 commented
   
   Fixed in [rev. 1242108](http://svn.apache.org/viewvc?rev=1242108&view=rev)
   
   The cause of this error is already in the beginning of the call, but only at 
the end it is causing trouble.
   The reason: while reproducing this issue the workDirectory is a single 
filename. When the commandline is built it first calls 
`workingDirectory.getParent()` and then it uses its `getAbsolutePath()`. In 
this order the parent can't be calculated, so when calling the 
`getAbsolutePath()` you'll get your NPE. If the workingDirectory was `rx/ry` 
you would have had no problem.
   




> NPE when workingDirectory is null
> ---------------------------------
>
>                 Key: SCM-641
>                 URL: https://issues.apache.org/jira/browse/SCM-641
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-client, maven-scm-provider-svn
>    Affects Versions: 1.5
>         Environment: Ubuntu Natty, JAVA_HOME = /usr/lib/jvm/java-6-sun
>            Reporter: Thibault Kruse
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 1.7
>
>
> $ maven-scm-client checkout rx 
> scm:svn:https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1
> [INFO] Executing: /bin/sh -c svn --non-interactive checkout 
> https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1 /home/tk/work/rx
> Error while executing the SCM command.
> org.apache.maven.scm.ScmException: Exception while executing SCM command.
>         at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
>         at 
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
>         at 
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
>         at 
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428)
>         at 
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405)
>         at 
> org.apache.maven.scm.manager.AbstractScmManager.checkOut(AbstractScmManager.java:399)
>         at 
> org.apache.maven.scm.client.cli.MavenScmCli.checkOut(MavenScmCli.java:238)
>         at 
> org.apache.maven.scm.client.cli.MavenScmCli.execute(MavenScmCli.java:190)
>         at 
> org.apache.maven.scm.client.cli.MavenScmCli.main(MavenScmCli.java:154)
> Caused by: java.lang.NullPointerException
>         at 
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:86)
>         at 
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
>         at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>         ... 8 more



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to