maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Lang (JIRA)" <>
Subject [jira] Updated: (SCM-338) NullPointerException when using -DvssDirectory to set ss.exe path
Date Sun, 02 Sep 2007 20:55:11 GMT


Allan Lang updated SCM-338:

    Attachment: SCM-338-[02]-maven-scm-provider-vss.patch

Updated patch {{SCM-338-[02]-maven-scm-provider-vss.patch}} includes a new test case for the
{{VssCommandLineUtils}}, which previously didn't have one.

The test needs to manipulate the {{~\.scm\vss-settings.xml}} file on disk, which may be a
bit suspect depending on how the project is build in CI, so please take a look at what's going
on in {{VssCommandLineUtilsTest}}.

> NullPointerException when using -DvssDirectory to set ss.exe path
> -----------------------------------------------------------------
>                 Key: SCM-338
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-vss
>    Affects Versions: 1.0
>         Environment: Windows XP, JRE 1.4.2
>            Reporter: Allan Lang
>            Priority: Minor
>         Attachments: SCM-338-[02]-maven-scm-provider-vss.patch, SCM-338-maven-scm-provider-vss.patch,
> NullPointerException occurs with any SCM operation when there is no ~/.scm/vss-settings.xml
file, and when the vssDirectory system property is set:
> {code}
> Caused by: java.lang.NullPointerException
>         at org.apache.maven.scm.provider.vss.commands.VssCommandLineUtils.getSettings(
>         at org.apache.maven.scm.provider.vss.commands.VssCommandLineUtils.getSsDir(
>         at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(
>         at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(
>         at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(
>         at org.apache.maven.scm.command.AbstractCommand.execute(
>         ... 21 more
> {code}
> This error is easily replicated using the attached project Unzip
the archive and run 
> {code}
> mvn scm:changelog -DvssDirectory=something -e
> {code}
> Assuming the file ~/.scm/vss-settings.xml does not exist, you should see the above error
in the stack traces. Note that you don't need VSS installed (or even to be on Windows) in
order to replicate the error - Maven doesn't actually get as far as making a call to ss.exe.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message