I’ve reimplemented the JUnit runner of Trinidad to talk to the latest FitNesse code (and use -c command execution path). The Maven plugin is also working. I’d appreciate if people could test this and see if it still works for them as the old trinidad support was dropped from the FitNesse trunk and will not be supported in the next release.
The beta build of fitnesse trunk can be downloaded using maven from
<dependency> <groupId>org.fitnesse</groupId> <artifactId>fitnesse</artifactId> <version>20091221-SNAPSHOT</version> </dependency>
Or alternatively download the binary jar directly.
The API is almost the same but some arguments are now obsolete, such as the test engine type. Because tests are executed using FitNesse -c directly, whatever is the selected engine type for the page will be used.
See JUnit Helper examples and FitNesseSuite runner examples with nice reporting for graphical JUnit tools
The Maven plugin also works, grab it from the same maven repository and use version 20091221-SNAPSHOT. Engine type parameter is obsolete and removed. See an example of how to use the plugin or how to directly invoke the target.

