Thank you Alex! It worked now. I had forgot to add the
jbehave-site-resources dependency.
But I get this XML error in Eclipse:
Plugin execution not covered by lifecycle configuration:
org.jbehave:jbehave-maven-plugin:4.0-beta-3:unpack-
view-resources (execution: unpack-view-resources, phase: process-resources)
I tried it with different versions of jbehave-maven-plugin, still I get
that error message displayed in the XML editor and in the problem view.
Why is that? It works, but it does not look good if Eclipse shows 1 error
in the POM XML file.
By the way, I have found no documentation on this on the JBehave site.
2013/10/5 Alex Filatau <fila...@gmail.com>
> I might be missing the question, but that's what working for me out of the
> box, by deploying jbehave with maven artifact.
> You need following dependency:
>
> <dependency>
>
> <groupId>org.jbehave.site</groupId>
>
> <artifactId>jbehave-site-resources</artifactId>
>
> <version>${jbehave.site.version}</version>
>
> <type>zip</type>
>
> </dependency>
>
> And then you need for your jbehave-maven-plugin add following execution:
>
>
> <execution>
>
> <id>unpack-view-resources</id>
>
> <phase>process-resources</phase>
>
> <goals>
>
> <goal>unpack-view-resources</goal>
>
> </goals>
>
> </execution>
>
>
> That's it. It results in target/jbehave directory to get images and css
> etc in my case.
>
> Or were you asking about customization of all this?
>
>
> Regards,
>
> Alex Filatau.
>
>
> On Fri, Oct 4, 2013 at 7:54 AM, Hans Schwäbli <
> bugs.need.love....@gmail.com> wrote:
>
>> The test result report of JBehave are HTML files.
>>
>> Unfortunately the referenced images and CSS file is not present in the
>> target folder.
>>
>> I spend quite some time figuring out how to add these resources by some
>> Maven configuration, but I could not get it working.
>>
>> Is there a small example for dummies showing how to do it? Please with no
>> parents, really simple POM file or snippet please.
>>
>
>
