Allow excluding plugins.properties from deletion by the set-up goal.

[GoogleCodeExporter]

Since we use SymbolicLinks in our test page hierachy, and SymbolicLinks cannot 
be nested, we are not using the <createSymLink> option in 
fitnesse-launcher-maven-plugin. Instead, we use src/test/fitnesse as 
<workingDir>, and use .gitignore for everithing else than our own test page 
hierarchy.

In src/test/fitnesse, we also have a plugins.properties file (since we use the 
SlimTables plugin to specify a couple of custom Slim table types). This 
combination however doesn't work, since fitnesse-launcher-maven-plugin for some 
reason in the "clean" stage of the set-up goal explicitly removes 
plugin.properties from <workingDir>.

Is it really necessary to remove plugins.properties from <workingDir> in order 
to get a clean setup? I can't see that it is getting expanded from fitnesse.jar.

If it needs to be removed, then we would need a way to override this behavior, 
preferably using a property.

Attached are two patches. The first patch removes the explicit deletion of 
plugins.properties. The second, alternative patch instead adds a configuration 
property to override the deletion.

Original issue reported on code.google.com by bjorn.be...@callistaenterprise.se on 4 Aug 2013 at 8:29

Attachments:

• dont-delete-plugins-properties.patch
• override-delete-plugins-properties-using-config-property.patch

[GoogleCodeExporter]

Original comment by stewart@javahelp.co.uk on 4 Aug 2013 at 8:39

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by stewart@javahelp.co.uk on 10 Jun 2014 at 1:09

• Added labels: Release-1.4.0

[GoogleCodeExporter]

Committed to /trunk at r396

Original comment by stewart@javahelp.co.uk on 23 Jun 2014 at 3:35

• Changed state: Fixed