Maven Build Error

[Robert]

Here is a list of the tools I am using to test an in-house web
application

Eclipse (with the easyb and Groovy plugins)
Selenium 1.0
easyb 0.9.7
Maven2

When I run a particular story within Eclipse using the easyb plugin
(e.g., using the Run As -> Behavior feature), the test works just
fine. However, when I attempt to run the test through Maven, using
the terminal (mvn -X test), I get the following error. The reference
to the "sessionId should not be null" pertains to Selenium. For some
reason, Selenium loses the session. The stack trace shown below seems
to be pointing to an issue with Maven, but I'm not entirely sure about
that.

[java] Running create an ad location story
(CreateAnAdLocation.story)
[java] FAILURE Scenarios run: 1, Failures: 1, Pending: 0, Time
elapsed: 26.091
sec
[java] scenario "A Business Manager should have permission to
create a new Ad
Location"
[java] step "a Business Manager has navigated to the Create a
New Ad Location page" -- ERROR Server Exception: sessionId should not
be null; has this session been started
yet?
[java] scenario "A Business Manager should have permission to
create a new Ad
Location"
[java] step "enters the required information into the form "
-- Cannot invoke method enterAdLocationName() on null
object
[java] scenario "A Business Manager should have permission to
create a new Ad
Location"
[java] step "the Business Manager clicks the Save button" --
Cannot invoke method clickSaveButton() on null
object
[java] scenario "A Business Manager should have permission to
create a new Ad
Location"
[java] step "a new Ad Location record is created" -- Cannot
invoke method getStatusFromAdLocationName() on null
object
[java] scenario "A Business Manager should have permission to
create a new Ad
Location"
[java] step "an 'Ad Location was successfully created.'
notification is displayed" -- Cannot invoke method
getSuccessfulNotification() on null
object
[java] 2 total behaviors ran with 1
failure
[java] Java Result:
255
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD
FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] 1 behaviors
failed
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: 1 behaviors failed
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:
556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:
348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:
180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: 1 behaviors
failed
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:
27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:
513)
at
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:
77)
at
org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:
71)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1470)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1400)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(InvokerHelper.java:
774)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBytecodeAdapter.java:
220)
at org.easyb.maven.EasybExecutor.execute(EasybExecutor.groovy:
55)
at org.easyb.maven.EasybMojo.execute(EasybMojo.java:139)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
694)

Has anybody seen this sort of error before? Any suggestions as to a
solution or workaround?

Thanks.