Hi Gijs, The main lack of the plugin is that it has not been updated with latest FitNesse evolutions (since 2008), this is due to the fact that I'm not having time at the moment for developing the plugin any more.
The features you mentionned was supported by the plugin (and old version of FitNesse), so it would be a pleasant contribution to update the plugin with new FitNesse versions. If I don't have enough time for developing it, I will find time for applying and release it if you provide some patches. - Using maven classpath for your tests : This is the aim of the classPathProvider http://mojo.codehaus.org/fitnesse-maven-plugin/run-mojo.html#classPathProvider. It may not add the sourcePath of the current project, as it at been design for a multimodule project, and features located in a specific maven project. But it may evolve on this part. This feature has been build for being able to locally run code under development with a remote FitNesse page, before the Eclipse FitNesse integration. - "In the near future I would like the plugin to be able to execute the fitnesse tests as part of the build process." That done with the plugin, the 'run' phase run the tests (you can fail the build in case of case failure if you want - with failOnError parameter - , but it's not usual), and the report phase agregate the result on you maven site (useful for nightly build report) The 2 main features of you requirements seems to be covered on the old versions. If you already was codehaus commiter you may take the lead of the plugin, if not I will be happy to apply to patches and provide support to you for starting to develop on the plugin. You will find codehaus conventions here http://mojo.codehaus.org/contribution/submitting-a-patch.html, they are important for beeing able to apply patches. Regards, Philippe On Mon, May 16, 2011 at 4:03 PM, Gijs Sijpesteijn < [email protected]> wrote: > Hi, > > I'm working on a Maven Fitnesse plugin. I know there are already two > similar plugins, fitnesse-maven-plugin and trinidad, but the first is hardly > maintained anymore and the later is missing some functionality and the > latest release is from 2010. > When running Fitnesse, you will need to specify the classpath for Fitnesse > to use. This classpath is almost identical as the maven classpath. Maven is > therefor perfect to extract this classpath and supply it to fitnesse. The > plugin will generate the classpath for fitnesse. The plugin can be > configured to include the /target/classes/ directory instead of a compiled > jar. Jar's can be excluded, resources can be specified and static entries > for the classpath for Fitnesse can be specified. > The big advantace is that you do not have to maintain the version of your > jar's to be maintained by hand, but will be generated as part of the maven > build cycle. > In the near future I would like the plugin to be able to execute the > fitnesse tests as part of the build process. (Similar to the trinidad > plugin). > At the moment, I'm working for a financial customer and we are using our > plugin with great success. I would really like this plugin to be shared with > of the world, since I think there are developers out there facing the same > problems. > > Cheers, Gijs Sijpesteijn > -- Philippe Kernévez Directeur technique (Suisse) [email protected] +41 79 888 33 32 Retrouvez OCTO sur OCTO Talk : http://blog.octo.com OCTO Technology http://www.octo.com
