[ 
https://jira.codehaus.org/browse/SCM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358706#comment-358706
 ] 

Jörg Hohwiller edited comment on SCM-585 at 12/6/14 6:30 AM:
-------------------------------------------------------------

No feedback after 4 years now... Is maven-scm a dead project?
How does maven update an svn repo after it is checked out? Not at all? Is there 
a pattern and I am just not seeing how to use the API properly?


was (Author: hohwille):
No feedback after 4 years now... Is maven-scm a dead project?
How does maven checkout from scratch? Is there a pattern and I am just not 
seeing how to use the API properly?

> "repository cannot be null" on ScmManager.makeProviderScmRepository(String, 
> File)
> ---------------------------------------------------------------------------------
>
>                 Key: SCM-585
>                 URL: https://jira.codehaus.org/browse/SCM-585
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-api
>    Affects Versions: 1.4
>            Reporter: Jörg Hohwiller
>
> I want to update a subversion with maven-scm.
> Therefore I get the ScmManager via Plexus and then do this:
> {code}
> ScmManager.makeProviderScmRepository("svn", new File(path/to/checkout));
> {code}
> What I get is:
> {noformat}
> java.lang.NullPointerException: repository cannot be null
>       at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:49)
>       at 
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
>       at 
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.info(AbstractSvnScmProvider.java:377)
>       at 
> org.apache.maven.scm.provider.svn.svnexe.SvnExeScmProvider.getRepositoryURL(SvnExeScmProvider.java:150)
>       at 
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.makeProviderScmRepository(AbstractSvnScmProvider.java:119)
>       at 
> org.apache.maven.scm.manager.AbstractScmManager.makeProviderScmRepository(AbstractScmManager.java:267)
> {noformat}
> From what I understand the code tries to execute "svn info" to get the 
> repository URL.
> However executing a command always checks that the repository is not {{null}}.
> In this case the svn command should be executed in order to be able to create 
> the repository.
> It is not possible to create the repository before, because the URL is not 
> known.
> My suggestion is to revisit this block in AbstractCommand:
> {code}
>         if ( repository == null )
>         {
>             throw new NullPointerException( "repository cannot be null" );
>         }
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to