Re: Is Jira 389 back with jbehave 3.5.2?

Hi Per, 

the solution in JBEHAVE-389 was to replace spaces with %2520.  

How/why does this not work for you?   Can you send us a sample project 
that reproduces your problem?

Alternatively, you can write your own path finder and use in place of 
StoryFinder.    If you extends JUnitStories you need to override the 
method storyPaths() to specify your own paths.

Cheers

On Wed Nov  9 11:08:49 2011, Per Newgro wrote:
> Hello,
>
> i'm evaluating jbehave as a candiate for our atdd test tool. What i've 
> done so far
> is creating a quickstart project by using the maven artifact of 
> jbehave-spring in eclipse.
> Everything works fine until i executed a mvn clean compile 
> integration-test. The result was
> that no story was executed.
>
> If i debug the quickstart MyStories by eclipse-junit runner i can see 
> that my absolute classes
> folder D:\Dokumente und Einstellungen\newgro\Eigene 
> Dateien\workspaces\poc\jbehave\target\classes
> is translated to
>
D:\Dokumente%2520und%2520Einstellungen\rene.d\Eigene%2520Dateien\workspaces\poc\jbehave\target\classes 
>
> by org.jbehave.core.io.CodeLocations.codeLocationFromClass(Class<?>).
>
> I search for problems and found 
> http://jira.codehaus.org/browse/JBEHAVE-389 . But it should be solved 
> with 3.2.
>
> Can somebody give me a hint how i can make this work.
>
> PS: I don't like to move my workspace to a non-whitespace folder.
>
> Cheers
> Per
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email