Hi, reason is that the jbehave reports are meant for the default life cycle (primarily for CI) and not for the site one.
If you want to contribute the report plugin we'll be happy to consider it. Cheers On 30 Nov 2012, at 13:32, Xavier Dury <[email protected]> wrote: > Hi, > > I've been evaluating JBehave for a couple of days and so far I like what I > can do with it. > > There is something though that I don't really understand concerning the maven > plugin: > > I don't understand why the generated reports are not fully integrated with > the maven-site-plugin, I would like to see a link to the JBehave report in > the "Project Reports" section. > > Nor do I understand why there's a goal like "unpack-view-resources"... > > I think those 2 problems could be resolved with some sort of > jbehave-maven-report-plugin that would create the jbehave report inside the > target/site folder (fully styled) and add a link to the "Project Reports". > > What do you think? > > Regards, > > Xavier > > >
