search

Enovea / fitnesse-launcher-maven-plugin

Automatically exported from code.google.com/p/fitnesse-launcher-maven-plugin
0 stars 0 forks source link

Fork option #37

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi,

I'm trying to integrate Fitnesse in our maven lifecycle.
We need to include jacoco in our integration test execution.
But for this we need to fork from Maven JVM.
I download your code and I see you use an option to set runInProcess to false.

May I suggest to add a 'fork' attribute in your run-tests goal in your next 
1.4.3 release like the maven compiler plugin do.

Please find attach the modification.

Regards,
Edouard Lemaistre

Original issue reported on code.google.com by edouard....@enovea.net on 25 Aug 2014 at 8:53

Attachments:

GoogleCodeExporter commented 8 years ago 
This code is to a large extent copied from FitNesse code. As well as not being 
100% sure what effect this change will have, it has also tended to change from 
release to release in the past.
In past versions of FitNesse, "debug mode" was necessary on the JUnit runner to 
prevent FitNesse falling into wiki mode - which was definitely a weirdness. It 
was also previously not clear that "debug mode" was the same thing as running 
in process.
Maybe with newer versions of FitNesse this is not so, but documentation is 
sparse.
Currently 1.4.3-SNAPSHOT is not well tested and had been problematic after 
trying to fit it to the next FitNesse release.
See: 
uk.co.javahelp.maven.plugin.fitnesse.mojo.RunTestsMojo.runFitNesseTests(Launch..
.)

Original comment by stewart@javahelp.co.uk on 10 Sep 2014 at 5:30