search

marcarvalho / fitnesse-launcher-maven-plugin

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

Easy config for copying plugins.properties and other FitNesse wiki pages, instead of verbose maven-resources-plugin:copy-resources #33

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Some projects may prefer to avoid using FitNesse SymLink to hook in their test 
suites into the FitNesse working directory.

A project can set '<createSymLink>true</createSymLink>' and then use 
maven-resources-plugin:copy-resources to copy specific FitNesse wiki pages into 
/target/fitnesse/FitNesseRoot.

Even if a project does use SymLinks, this would also still have to be done for 
the correct deployment of plugins.properties.

The current (1.4.0) java example project shows both of these examples in the 
pom.xml, but it is very verbose configuration.

For convenience, we could perhaps have some config similar to:
  <plugin>
      <groupId>uk.co.javahelp.fitnesse</groupId>
      <artifactId>fitnesse-launcher-maven-plugin</artifactId>
      <configuration>
          <pluginsProperties>
              <copy-resource>true</copy-resource>
              <location>src/test/fitnesse</location>
              <!-- See also Issue #22, regarding cleanup of plugins.properties -->
          </pluginsProperties>
<!-- Would copy MyTestSuite + all children to top of ${fitnesse.workingDir} -->
          <wiki>MyTestSuite</wiki>
<!-- Would copy AnIndividualTest correctly nested to 
${fitnesse.workingDir}/MyTestSuite/NestedSuite/AnIndividualTest -->
          <wiki>MyTestSuite.NestedSuite.AnIndividualTest</wiki>
 <!-- Would copy AnIndividualTest un-nested to top, as in ${fitnesse.workingDir}/AnIndividualTest -->
          <wiki>MyTestSuite/NestedSuite/AnIndividualTest</wiki>
      </configuration>
  </plugin>

Original issue reported on code.google.com by stewart@javahelp.co.uk on 4 Jul 2014 at 9:31

GoogleCodeExporter commented 9 years ago 
See also Issue #31 - need to make sure these two features don't clash

Original comment by stewart@javahelp.co.uk on 4 Jul 2014 at 9:33