Re: [jbehave-user] NPE at org.jbehave.core.configuration.Configuration.doDryRun(Boolean)

2014-06-18 Thread Mauro Talevi
Applied with thanks. On 18/06/2014 08:53, Hans Schwäbli wrote: I attached a patch for this in this email (for 4.x branch). On Wed, Jun 11, 2014 at 11:41 AM, Mauro Talevi mailto:mauro.tal...@aquilonia.org>> wrote: Lazy init may still have some teething issues. Please provide a patch

Re: [jbehave-user] NPE at org.jbehave.core.configuration.Configuration.doDryRun(Boolean)

2014-06-17 Thread Hans Schwäbli
I attached a patch for this in this email (for 4.x branch). On Wed, Jun 11, 2014 at 11:41 AM, Mauro Talevi wrote: > Lazy init may still have some teething issues. Please provide a patch. > > > > On 11 Jun 2014, at 10:46, Hans Schwäbli > wrote: > > > > Hello Mauro, > > > > today I had a NullPo

Re: [jbehave-user] NPE at org.jbehave.core.configuration.Configuration.doDryRun(Boolean)

2014-06-11 Thread Mauro Talevi
Lazy init may still have some teething issues. Please provide a patch. > On 11 Jun 2014, at 10:46, Hans Schwäbli wrote: > > Hello Mauro, > > today I had a NullPointerException at > org.jbehave.core.configuration.Configuration.doDryRun(Boolean) with JBehave > beta-6. > > It was because th

[jbehave-user] NPE at org.jbehave.core.configuration.Configuration.doDryRun(Boolean)

2014-06-11 Thread Hans Schwäbli
Hello Mauro, today I had a NullPointerException at org.jbehave.core.configuration.Configuration.doDryRun(Boolean) with JBehave beta-6. It was because this.storyControls was null. Why don't you use storyControls().doDryRun(dryRun) instead of this.storyControls.doDryRun(dryRun)? Because the insta