I'm getting an NPE when running the command "scm status" in certain circumstances.

The message from the .log file is at the end of the post.

I'm using RTC 1.01 using the scm tool from the 1.01 RTC client and the 1.01 server.

The problem is doing an scm status with a workspace loaded automatically from the build.

I have another workspace checked out manually (using scm load from RTC 1.00) which works fine. If I manually load a workspace using RTC 1.01 scm load it works fine and doing an scm status on it works fine.

Is the automatically loaded build workspace in some way different from a normal load? I notice the automatically loaded version doesn't have a .metadata folder otherwise it is identical to a manually loaded workspace. I checked using WinMerge.

Any help appreciated.

Cheers, Chris.

!SESSION 2008-11-14 13:39:42.727 -----------------------------------------------

eclipse.buildId=unknown

java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20080315 (JIT enabled)

J9VM - 20080314_17962_lHdSMr

JIT  - 20080130_0718ifx2_r8

GC   - 200802_08

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB

Framework arguments:  status

Command-line arguments:  -os win32 -ws win32 -arch x86 -data @noDefault status



!ENTRY org.eclipse.osgi 4 0 2008-11-14 13:39:46.727

!MESSAGE Application error

!STACK 1

java.lang.NullPointerException

	at com.ibm.team.filesystem.cli.core.util.RepoUtil.getWorkspaceConnections(Unknown Source)

	at com.ibm.team.filesystem.cli.core.util.PendingChangesUtil.printPendingChanges(PendingChangesUtil.java:249)

	at com.ibm.team.filesystem.cli.client.internal.subcommands.StatusCmd.run(StatusCmd.java:90)

	at com.ibm.team.filesystem.cli.core.internal.Application.run(Unknown Source)

	at com.ibm.team.filesystem.cli.core.internal.Application.doStart(Unknown Source)

	at com.ibm.team.filesystem.cli.core.internal.Application.start(Unknown Source)

	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)

	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)

	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:618)

	at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)

	at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)

	at org.eclipse.equinox.launcher.Main.run(Unknown Source)



!ENTRY org.eclipse.osgi 2 0 2008-11-14 13:39:46.743

!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:

!SUBENTRY 1 org.eclipse.osgi 2 0 2008-11-14 13:39:46.743

!MESSAGE Bundle initial@reference:file:plugins/org.eclipse.core.filesystem.linux.x86_1.1.0.v20070416.jar/ [67] was not resolved.

!SUBENTRY 2 org.eclipse.core.filesystem.linux.x86 2 0 2008-11-14 13:39:46.743

!MESSAGE Platform filter did not match: (& (osgi.os=linux) (osgi.arch=x86))